-
Notifications
You must be signed in to change notification settings - Fork 188
JS-652 Changing the dependency of meta and generated-meta #5217
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
Conversation
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.
-500 lines, still valuable :)
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.
Looks good to me. some points:
- for me
npm ci
is a prerequisite. we should have dependencies installed:- no need to run npx in scripts
- we can always prettify
- seems changes on the git submodules have been pushed. can you run
git submodules update
locally? I don't think there have been changes on them lately so so may have an old commit locally. In any case, don't add them to this PR pls
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.
Thats' great, thank you. We will all benefit from the reduced build duration.
|
JS-652
As this was a bit out of order, we should not have hand written code depend on generated code. This way, we can access
meta.js
before thegenerated-meta.js
is presented.With these changes, I was able to remove the dependency of
javascript-checks
onbridge
. This way, the bridge starts building instantly when using the parallel option of maven build!