Mechanisms to persist hierarchical object relations
View Patent ↗Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.
1. A method implemented in a non-transitory machine-readable medium and for execution on a processor and memory-enabled device, comprising:
receiving, by the processor and memory-enabled device, a load instruction for a first object of a project;
loading, by the processor and memory-enabled device, a first file for the first object within a root directory for the project;
identifying, by the processor and memory-enabled device, relationships for one or more second objects that derive from the first object via subdirectories defined under the root directory;
loading, by the processor and memory-enabled device, one or more second files that define the one or more second objects from the subdirectories to create a processing environment for the project to process;
detecting, by the processor and memory-enabled device, a new third object that is created while processing the project within the project processing environment;
determining, by the processor and memory-enabled device, a context within which the new third object was created that identifies the new third object as being a child to a particular second object that previously had no children;
creating, by the processor and memory-enabled device, a second subdirectory within a particular subdirectory associated with the particular second object, wherein the second subdirectory is named using an identifier for the particular second object; and
storing, by the processor and memory-enabled device, a third file that defines the new third object within the second subdirectory to establish a parent-child relationship between the new third object and the particular second object.
2. The method of claim 1 , wherein receiving further includes resolving an identity for the project to acquire another identity for the first object that then identifies the root directory and the first file, which is named using the identity for the first object within the root directory.
3. The method of claim 1 , wherein identifying further includes establishing the relationships between the first object and the one or more second objects via a presence of the subdirectories within the root directory.
4. The method of claim 1 , wherein identifying further includes recursively traversing the subdirectories to identifying nested relationships between the one or more second objects with one another, wherein at least one subdirectory includes another one of the subdirectories that identifies a particular one of the nested relationships.
5. The method of claim 1 further comprising:
detecting, by the processor and memory-enabled device, a deletion of a particular second object while processing the project within the project processing environment;
locating, by the processor and memory-enabled device, a particular subdirectory associated with the particular second object; and
removing, by the processor and memory-enabled device, the particular subdirectory.
6. The method of claim 1 further comprising:
detecting, by the processor and memory-enabled device, a particular second object as having a dependency changed while processing the project within the project processing environment; and
moving, by the processor and memory-enabled device, a particular subdirectory associated with the second object from an existing location to a new location to reflect the changed dependency without modifying any instructions associated with the particular second object or the project as a whole.