Final updates before release #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the first commit, lodash 8.0.0 has eslint@>=9.0.0 as a peer dependency so I downgraded (lodash v8 also seems to haven be taken over by an individual from the previous maintainer(s); I didn't look further into it)
I tested this in 2 repos:
ois- where there are a lot of lints, but most are decent and/or can be fixed with--fixcommons/eslintfunctionality (universalandjest) - I replaced the local import with this plugin and no new errors were raised besides 3 newUnused eslint-disable directivethat result from a@typescript-eslintpackage version bump between this repo and eslint within commons.which means after this is merged, I think we're ready for release and use.