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
refactor: Update reference.json to use relative paths #1251
Conversation
Codecov ReportPatch coverage is
📢 Thoughts on this report? Let us know!. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing job, so clean. This will also make it easier to run tests on feature-branches where you want to copy over an existing cache and make some changes, now you don't need to modify the reference.json anymore! Just point to the new path. Sweet! : )
⭐ 🌟 ⭐ 🌔 ⭐ ⭐ ⭐
🌲 🌲 🌲 🌲 🌲 🌲 🌲
🦖 🦖 🦖 🦖 🦖 🦖 🚒
Co-authored-by: Mathias Johansson <math.joh.bio@gmail.com>
Co-authored-by: Mathias Johansson <math.joh.bio@gmail.com>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This PR:
In order to be able to copy the balsamic cache from stage to production, we need to start saving the cache reference file links as relative paths (
reference.json
).To maintain simplicity, the
config.json
reference file will continue to point to stage files, as the cache will be built primarily in the stage from this point onward.Changed:
reference.json
file to use relative pathsReview and tests:
Tests pass
balsamic init
. Saves relative paths.balsamic config case
. Reads relative paths, but saves them as absolute.Code review
New code is executed and covered by tests, and test approve