Central registry for binding features using dynamic pointers
View Patent ↗A first feature (e.g., chart or table) includes a reference to a dynamic pointer. Independently, the pointer is defined to point to a second feature (e.g., a query). The first feature is automatically updated to reflect a current value of the second feature. The reference to the pointer and pointer definition are recorded in a central registry, and changes to the pointer or second feature automatically cause the first feature to be updated to reflect the change. A mapping between features can be generated using the registry and can identify interrelationships to a developer. Further, changes in the registry can be tracked, such that a developer can view changes pertaining to a particular time period and/or feature of interest (e.g., corresponding to an operation problem).
1. A non-transitory computer-readable medium storing instructions that, when executed by a client computing device, cause performance of:
responsive to determining that app features have been created, automatically registering the app features within a registry as a referring feature, a target feature, or both a target feature and a referring feature;
responsive to detecting that a referring feature of the app features is bound to a target feature of the app features, automatically registering, within the registry, the referring feature to receive notifications of events pertaining to the target feature;
responsive to detecting a change associated with the target feature:
identifying relevant app features of the app features that are registered to receive notifications about events pertaining to the target feature, wherein the relevant app features include the referring feature; and
notifying the relevant app features about the change associated with the target feature.
2. The non-transitory computer-readable medium of claim 1 , wherein the change associated with the target feature includes at least one of:
a new registration of the target feature;
a change to the target feature's definition;
a change to the target feature; or
a removal of the target feature.
3. The non-transitory computer-readable medium of claim 1 , wherein the referring feature is configured to respond to the notifying the relevant app feature by updating data presented by the referring feature to reflect data in the target feature.
4. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the client computing device, further cause performance of tracking a history of modifications to the registry.
5. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the client computing device, further cause performance of:
tracking a history of events associated with the registry; and
presenting a visual timeline of the events in the history.
6. The non-transitory computer-readable medium of claim 1 , wherein the instructions, when executed by the client computing device, further cause performance of generating a map of interrelationships between at least some of the app features.
7. The non-transitory computer-readable medium of claim 1 , wherein the target feature is configured to execute a search query that returns values, and wherein the referring feature is configured to execute code for displaying a chart or table based upon the values.
8. A method comprising:
sending one or more libraries of code to a client device, wherein the one or more libraries cause the client device to perform, during execution of application code that references the one or more libraries of code:
responsive to determining that app features have been created, automatically registering the app features within a registry as a referring feature, a target feature, or both a target feature and a referring feature;
responsive to detecting that a referring feature of the app features is bound to a target feature of the app features, automatically registering, within the registry, the referring feature to receive notifications of events pertaining to the target feature;
responsive to detecting a change associated with the target feature:
identifying relevant app features of the app features that are registered to receive notifications about events pertaining to the target feature, wherein the relevant app features include the referring feature; and
notifying the relevant app features about the change associated with the target feature.
9. The method of claim 8 , wherein the change associated with the target feature includes at least one of:
a new registration of the target feature;
a change to the target feature's definition;
a change to the target feature; or
a removal of the target feature.
10. The method of claim 8 , wherein the referring feature responds to the notifying the relevant app feature by updating data presented by the referring feature to reflect data in the target feature.
11. The method of claim 8 , wherein the one or more libraries of code further cause the client device to track a history of modifications to the registry.
12. The method of claim 8 , wherein the one or more libraries of code further cause the client device to:
track a history of events that modify the registry; and
present a visual timeline of the events in the history.
13. The method of claim 8 , wherein the one or more libraries of code further cause the client device to generate, based on the registry, a map of interrelationships between at least some of the app features.
14. The method of claim 8 , wherein the target feature executes a search query that returns values, wherein the referring feature executes code for displaying a chart or table based upon the values.
15. A system comprising:
one or more processors;
a data repository;
a data server to conduct searches upon the data repository;
a server to send one or more libraries of code to a client device;
wherein the one or more libraries cause the client device to perform, during execution of application code that references the one or more libraries of code:
responsive to determining that app features have been created, automatically registering the app features within a registry as a referring feature, a target feature, or both a target feature and a referring feature;
responsive to detecting that a referring feature of the app features is bound to a target feature of the app features, automatically registering, within the registry, the referring feature to receive notifications of events pertaining to the target feature;
responsive to detecting a change associated with the target feature:
identifying relevant app features of the app features that are registered to receive notifications about events pertaining to the target feature, wherein the relevant app features include the referring feature; and
notifying the relevant app features about the change associated with the target feature.
16. The system of claim 15 , wherein the change associated with the target feature includes at least one of:
a new registration of the target feature;
a change to the target feature's definition;
a change to the target feature; or
a removal of the target feature.
17. The system of claim 15 , wherein the referring feature responds to the notifying the relevant app feature by updating data presented by the referring feature to reflect data in the target feature.
18. The system of claim 15 , wherein the one or more libraries of code further cause the client device to track a history of modifications to the registry.
19. The system of claim 15 , wherein the one or more libraries of code further cause the client device to:
track a history of events that modify the registry; and
present a visual timeline of the events in the history.
20. The system of claim 15 , wherein the one or more libraries of code further cause the client device to generate, based on the registry, a map of interrelationships between at least some of the app features.