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
The names of the types are abstracted, being HRIDs withint the file, forming the intersection type.
However, it would be better to have a seperate tool in addition to the in-interface tools that allows managing the types in a power-user way.
To do this, JointOrigins assigned ID should just be mapped to their assignments, and those be stored in the Backend.
Project crawling still works, only the assigned types are now loaded in the backend, not the frontend.
The text was updated successfully, but these errors were encountered:
The capability is basically already there, it's more or less contained in the parts database.
We could load the part info on opening a file, and if there is a discrepancy prompt if we want to overwrite the part info with the backend stuff.
Also we could do a crawl to update all parts with the updated backend info if applicable, and keep a list of changes made directly.
Then we could introduce an UI that allows handling and fixing such issues with a user-specified resolution if a type has gone missing.
The names of the types are abstracted, being HRIDs withint the file, forming the intersection type.
However, it would be better to have a seperate tool in addition to the in-interface tools that allows managing the types in a power-user way.
To do this, JointOrigins assigned ID should just be mapped to their assignments, and those be stored in the Backend.
Project crawling still works, only the assigned types are now loaded in the backend, not the frontend.
The text was updated successfully, but these errors were encountered: