Metadata document updates for application development platform
A base application data store may contain a base application source metadata file with at least one extension point that defines a permission associated with the extension point in connection with a base application. An extension application server, coupled to the base application data store, retrieves the base application source metadata file and caches the base application source metadata file as a read only file. The extension application server then generates a merge map file with an extension change to the base application metadata file. The base application source metadata file and the merge map file may be, for example, merged in accordance with the defined permission to create a result metadata file for the base application. In some embodiments, the extension application server subscribes to application updates for the base application, and the extension change is reported and validated in accordance with the permission associated with extension point.
1 . A system associated with a metadata-based application development platform, comprising:
a base application data store containing a base application source metadata file with at least one extension point that defines a permission associated with the at least one extension point in connection with a base application; and
an extension application server, coupled to the base application data store, including:
a computer processor, and
a computer memory storing instructions that, when executed by the computer processor, cause the extension application to:
retrieve the base application source metadata file,
subscribe to application updates for the base application,
cache the base application source metadata file as a read only file,
automatically generate a merge map file with an extension change to the base application metadata file, and
report and validate the extension change accordance with the permission associated with the at least one extension point,
wherein the base application source metadata file and the merge map file are merged in accordance with the defined permission to create a result metadata file for the base application.
2 . The system of claim 1 , wherein an error is displayed to an extension developer in substantially real time when the extension change is incompatible with the permission.
3 . The system of claim 1 , wherein an error summary project report table is provided to a base developer for extension changes that were incompatible with the permission.
4 . The system of claim 1 , wherein the at least one extension point and permission are associated with a simple property and comprise an indication of which properties are allowed to be extended.
5 . The system of claim 1 , wherein the at least one extension point and permission are associated with an object property and comprise an ability to add, remove, or override an object property.
6 . The system of claim 1 , wherein the at least one extension point and permission are associated with an array property and an ability to reorder, remove, or insert information in an array.
7 . The system of claim 1 , wherein the base application source metadata file includes a plurality of extension points that each define at least one permission in connection with the base application.
8 . A computer-implemented method associated with a metadata-based application development platform, comprising:
retrieving, by a computer processor of an extension application server, a base application source metadata file from a base application data store, the base application source metadata file including at least one extension point that defines a permission associated with the at least one extension point in connection with a base application;
subscribing, by the computer processor of the extension application server, to application updates for the base application;
caching, by the computer processor of the extension application server, the base application source metadata file as a read only file;
automatically generating a merge map file with an extension change to the base application metadata file; and
reporting and validating the extension change accordance with the permission associated with the at least one extension point,
wherein the base application source metadata file and the merge map file are merged in accordance with the defined permission to create a result metadata file for the base application.
9 . The method of claim 8 , wherein an error is displayed to an extension developer in substantially real time when the extension change is incompatible with the permission.
10 . The method of claim 8 , wherein an error summary project report table is provided to a base developer for extension changes that were incompatible with the permission.
11 . The method of claim 8 , wherein the at least one extension point and permission are associated with a simple property and comprise an indication of which properties are allowed to be extended.
12 . The method of claim 8 , wherein the at least one extension point and permission are associated with an object property and comprise an ability to add, remove, or override an object property.
13 . The method of claim 8 , wherein the at least one extension point and permission are associated with an array property and an ability to reorder, remove, or insert information in an array.
14 . The method of claim 8 , wherein the base application source metadata file includes a plurality of extension points that each define at least one permission in connection with the base application.
15 . A non-transitory, machine-readable medium comprising instructions thereon that, when executed by a processor, cause the processor to execute operations to perform a method associated with a metadata-based application development platform, the method comprising:
retrieving, by a computer processor of an extension application server, a base application source metadata file from a base application data store, the base application source metadata file including at least one extension point that defines a permission associated with the at least one extension point in connection with a base application;
subscribing, by the computer processor of the extension application server, to application updates for the base application;
caching, by the computer processor of the extension application server, the base application source metadata file as a read only file;
automatically generating a merge map file with an extension change to the base application metadata file; and
reporting and validating the extension change accordance with the permission associated with the at least one extension point,
wherein the base application source metadata file and the merge map file are merged in accordance with the defined permission to create a result metadata file for the base application.
16 . The medium of claim 15 , wherein: (i) an error is displayed to an extension developer in substantially real time when the extension change is incompatible with the permission, and (ii) an error summary project report table is provided to a base developer for extension changes that were incompatible with the permission.