You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: For most of the map functionalities as well as a lot of the other data sources used in searching, the data is hardcoded in these json files. The contracts being read and used in most of the website are also manually put into the second source path which are then parsed during the setup script and broken into sentences, locations, etc.
Source: (Any branch) PPUC/frontend/src/data/[filename].json
Source: (Any branch) PPUC/PxPUC/static/app/contracts_txt
Description: For most of the map functionalities as well as a lot of the other data sources used in searching, the data is hardcoded in these json files. The contracts being read and used in most of the website are also manually put into the second source path which are then parsed during the setup script and broken into sentences, locations, etc.
Solution: This would ideally be moved to the mastersheet file to keep everything centralized. Currently, the read-in-spreadsheet branch uses the mastersheet for a few models and is closer to the ideal solution than other branches, but most of the site there too is hardcoded. See https://docs.google.com/presentation/d/1zLYKVh1x9FClBBR48DPjraotNEX04uCR/edit?usp=sharing&ouid=111268317828128026813&rtpof=true&sd=true
The text was updated successfully, but these errors were encountered: