ExternalVendorCode/openmct
1
0
Fork 0
mirror of https://github.com/nasa/openmct.git synced 2024-12-20 05:37:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
65325b90fd
openmct/platform/entanglement
History
Pete Richards 65325b90fd Composition policy takes child instance 
The composition policy now takes a child instance instead
of the child type, as in all cases we have access to the child
object.

This allows new-style objects to be contained by old-style objects.

Updated all composition policies to use standardized argument names
instead of `context` and `candidate`; this makes it easier to
understand.

Updated AddActionProvider to hardcode the object types supported.
2017-02-21 12:32:49 -08:00
..
src Composition policy takes child instance 2017-02-21 12:32:49 -08:00
test Merge remote-tracking branch 'origin/master' into persist-on-mutation-825 2016-10-07 11:27:58 -07:00
bundle.js [Frontend] Refactor glyphs to classes 2016-08-01 14:33:25 -07:00
README.md Typo corrections, I avoided making changes to words that have regional spelling differences. 2016-09-03 09:16:54 -04:00

README.md

Entanglement

Entanglement is the process of moving, copying, and linking domain objects in such a way that their relationships are impossible to discern.

This bundle provides move, copy, and link functionality. Achieving a state of entanglement is left up to the end user.

Services implement logic

Each method (move, copy, link) is implemented as a service, and each service provides two functions: validate and perform.

validate(object, parentCandidate) returns true if the object can be move/copy/linked into the parentCandidate's composition.

perform(object, parentObject) move/copy/links the object into the parentObject's composition.

Actions implement user interactions

Actions are used to expose move/copy/link to the user. They prompt for input where necessary, and complete the actions.