RFC: Reference validation #323
Labels
Component: Graph Manager
Issues related to graph processing and management (including interaction with engine server) logic
Studio Core Team
Opened by a member of the Studio core team
Type: Discussion
Type: Refactor
Milestone
One big concern we have is when we delete something, other parts of the app still keeps the reference to it. For example: class properties being referred to in class mappings, etc. Right now our strategy after deleting some element is quite inconsistent:
The former is a bit aggressive if we need to do this for every change. That being said, it might be useful to tell user when references are broken/invalid.
Implementation Plan
isDeleted
for places we want: element, property (basically for each type of reference)computed
property to each reference (potentially for reference we can do a methodisValid()
always returningtrue
by default, and we canoverride
for each as we start supporting more and more things) -> this is good for graph validation checks in general. See RFC: Rework graph feedback #262The text was updated successfully, but these errors were encountered: