fix: missed enums and typings from #7290 #7331
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
github-actions
bot
requested review from
iCrawl,
kyranet,
SpaceEEC and
vladfrangu
ImRodry
reviewed
Jan 23, 2022
iCrawl
approved these changes
Jan 24, 2022
SpaceEEC
approved these changes
Jan 24, 2022
kyranet
previously requested changes
Jan 25, 2022
|
Just realized this also fixes a bug, can you go ahead and edit your PR description to add: "Closes 7336" |
This was referenced Jan 25, 2022
vladfrangu
approved these changes
Jan 25, 2022
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.
Please describe the changes this PR makes and why it should be merged:
Some typings are out of date and a few enums are still being converted to strings. I also
{@link}ed the enums in the JSDocs, if you want me to revert that I will.Status and versioning classification: