-
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
Feature/ADF-1417/Upgrade to Node 18 #170
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.
looks nice, and no reported issued here :), lets go!
@@ -45,7 +45,7 @@ const errorHandler = { | |||
/** | |||
* Get a context by it's name and create it if it doesn't exists | |||
* @param {String} name - the context name | |||
* @returns {Object} the handling context | |||
* @returns {Object|undefined} the handling context | |||
*/ |
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 understand this task is just fixing the doc, so no issues, but wouldnt it be nice that this handler return null instead of undefined? :)
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.
Yes, actually it would be better to refactor the code in order to keep a consistent behavior.
But I did not want to change it, and only avoid adding lint error due to the version change
…F-1417/upgrade-to-node18
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.
Works good on my environment
Version
There are 0 BREAKING CHANGE, 0 feature, 1 fix |
Related to: ADF-1417 and ADF-1419
Requires:
package.json
once the companion PRs have been merged and releasedSummary
Update the devDependencies for supporting Node 18
Set Node 18 for the CI workflow.
Details
To properly support Node 18, the dev dependencies had to be updated and aligned.
Note: The lock file was generated with
npm@6
so it would also work seamlessly with Node 14.How to test
npm i
npm test
,npm run test:cov
,npm run coverage
npm run build
npm run lint:src
,npm run lint:test