Spliting the project config and misc tricks #69
j3k0
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For feeding future thoughts...
In my project I've decided to split the
project.apmfile into 2 different files:project/dependencies.jsoncontains{"dependencies": [...], "repositories": [...]}project/configuration.jsoncontains{"identifier":"<id>", "version": "1.0.0", "configuration": [...]}(basically all the rest).The reason is that this allows my build chain to only call
apm installwhenproject/dependencies.jsonis more recent than the content ofapm_packages.project.apmis generated by doingcat project/*.json | jq -s '.[0] * .[1]' > project.apmThis isn't built-in
apmso to install a dependency I manually edit thedependencies.jsonfile. I actually don't mind, editing JSON is totally fine with me.An idea for
apmto support this use case natively would be to allow using multipleproject.apmfiles:For example:
apm-project project/dependencies.jsoninstallapm-project project/configuration.jsonproject configapm-project project/configuration.json-project project/dependencies.jsongenerate app-descriptorAnother trick I use is to generate a
src/Version.asfile fromproject/configuration.json:This way I can show the users the version of the app they use in the corner of the screen.
Maybe would be a useful generator to add to
apmin the future?For reference, relevant parts of the
Makefile:Beta Was this translation helpful? Give feedback.
All reactions