-
Notifications
You must be signed in to change notification settings - Fork 273
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: rename modules
project config entry to scan
#4036
Conversation
b6941a7
to
1f94a78
Compare
7e2c88a
to
6c3835b
Compare
core/src/config/project.ts
Outdated
/** | ||
* Deprecated. Use {@link #scan} instead. | ||
* @deprecated remove in 0.14 | ||
*/ | ||
modules?: { |
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.
I think we should just remove this from the internal interface.
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.
Removed it in 905f8ac
6c3835b
to
905f8ac
Compare
core/src/config/base.ts
Outdated
} | ||
|
||
if (projectSpec["modules"].include) { | ||
const oldSyntaxInclusions = projectSpec["modules"].include || [] |
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.
Why not simply use the rename option in the joi schema? You can catch and emit the usage of the old field before validating.
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.
That was my initial plan. Should we deny using both fields simultaneously?
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.
Simplified this in 2966c7f
Use field renaming on the joi schema level.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #3512
Special notes for your reviewer: