-
Notifications
You must be signed in to change notification settings - Fork 0
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
Migrate plugin-config commands #4
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.
going to open a PR for some of this
"@salesforce/dev-config": "^3.1.0", | ||
"@salesforce/dev-scripts": "^2", | ||
"@salesforce/dev-scripts": "^2.0.4", |
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.
there's a newer dev-scripts that updates the general (non-plugin) linter rules. Using that now saves some extra work later.
It'll bump some other deps and clean up unused deps, too.
let value = ''; | ||
const configs = await this.parseConfigKeysAndValues(); | ||
for (const name of Object.keys(configs)) { | ||
try { | ||
value = configs[name]; |
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.
avoids let
, probably safe outside try/catch
let value = ''; | |
const configs = await this.parseConfigKeysAndValues(); | |
for (const name of Object.keys(configs)) { | |
try { | |
value = configs[name]; | |
const configs = await this.parseConfigKeysAndValues(); | |
for (const name of Object.keys(configs)) { | |
const value = configs[name] ?? ''; | |
try { |
some feedback in a PR: #5 |
What does this PR do?
Started with
plugin-template-sf
as a baseMigrated
plugin-config
v2
commandsWhat issues does this PR fix or reference?
@W-11572657@