feat: TS migration for GraphQL Resolvers #342
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
bagelbits
changed the title
| })), | ||
| starting_equipment_options: async (background: Background) => | ||
| background.starting_equipment_options.map(async option => { | ||
| if ('equipment_category' in option.from) { |
There was a problem hiding this comment.
Not sure if this if is necessary. Also, since it's inside a map function, it's a bit strange seeing that if the if failed the function wouldn't return a value.
There was a problem hiding this comment.
I had to do this in a lot places due to how types for choices are currently setup. Otherwise I get:
Property 'equipment_category' does not exist on type 'OptionSet'.
Property 'equipment_category' does not exist on type 'OptionsArrayOptionSet'.
|
🎉 This PR is included in version 2.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
What does this do?
How was it tested?
npm run buildand CIIs there a Github issue this is resolving?
No
Was any impacted documentation updated to reflect this change?
Yup!
Here's a fun image for your troubles