-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Generator artifacts] inherit attribute for generated files #315
Comments
It is up to the generator to set the RO attribute on files in the generator output (see Generator Integration). Two initial asks:
|
Hello, Here is an example of .psdc and .gpdsc implementing our proposal for an inherited modifiable attribute. attached the .pdsc and .gpdsc as example. |
@ameltalbi , thanks a lot for sharing this example. |
@jkrech |
The schema for a *.pdsc and *.gpdsc regarding
the "modifiable" attribute is used for a regular C source file and what it means for a source file is currently not defined. |
@jkrech, Yes you are right, that's why we request that this attr="modifiable" is to be allowed (valid) only in a .gpdsc file. |
The Problem To Be Solved
The principle of read-only “Generator artifacts” is that generated code is fully managed by the generator, so that generated files are in read-only mode access (earased and regenerated from scratch when regenerate).
Nevertheless, we need to consider the case of generated files that need to be modified by user to manage its application part, like “generated user templates”
==> Generator artifacts could be also modifiable (same as configuration file)
The need is to be able to tag modifiable generated files.
Accordingly we need to introduce a mechanism so that attributes are inherited to generated file (generated based on a "genAsset" file).
Suggest A Solution
Add a new child element named "inherited" to be added to
<file>
with attribute "category" set togenAsset
from where generated file will inherit attributes defined inside.example:
these attributes should be then transferred as attributes of the generated file inside the .GPDSC (similar solution will be also needed for .cgen.yml option)
The text was updated successfully, but these errors were encountered: