chore: manually clean graphql-transformer-core on each build to avoid type override issues #477
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.
Description of changes
manually clean graphql-transformer-core on each build to avoid type override issues, this is a mitigation, not a solution.
I'll create an item in the backlog to dig into this later, but for now this unblocks happy-case development paths without needing to manually rebuild the env on each change.
Issue #, if available
N/A
Description of how you validated changes
Ran build a great many times in a row, ran setup-dev a few times, and ran unit tests.
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.