-
Notifications
You must be signed in to change notification settings - Fork 18
Metadata generator V2 #113
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
base: master
Are you sure you want to change the base?
Metadata generator V2 #113
Conversation
Update the metadata-generator for More app V2
|
To deploy only after the release of the new qml More app. |
Add info about "template applications repository"
|
Please |
I cannot do that because I don't have the required permissions. You should be able to do it though: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account |
Code Adjustments
Done: overte-org / template_Applications_Repository |
Update the guidelines about dependencies and licenses We allowed external server/service dependancies if essential Precision about licenses (open-souce allowing modification) See the text in the file.
This retake the PR#107 which wouldn't have worked completely anyway.
This is the new metadata generator for the application repository V2
Changes done over the work initiated in PR107:
Removal of the repository selector. It was a nice idea to want to edit any repository using this metadata generator but the truth is that web js is not allowed to bring the content of a JSON from outside its domain. It was certainly worki8ng during the development, but if you try to read a repository elswhere, it was not working. (Is wasn't for no reason that it was a .js before, and not a .json)
So the generator is now simple operate on the ../applications/metadata.json
I will provide a repository template on github that will include the generator, it will be easier for people to start their repository from it.
Removal of the support for the Legacy in the generator.
We won't use that after. It became irrelevant as we only edit metadata.json. The original metadata.j will stay present for a time for old versions.
More documentation about the data to capture in the create application form