fix: mutation validator and trigger cyclic import structure #118
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.
Why
Similar to #89 and #93, we need to do the same for validators and triggers in case those import entities themselves.
I tried rethinking this whole thing and just making the companion definition a function (
static getCompanionDefinition(): () => EntityCompanionDefinition
) but it made things less clean to define (had to remove top-level consts containing companion definitions to reap benefits) and made things less composable (because consts are no longer possible, can't be shared).How
Make the params functions similar to other PR examples above.
Test Plan
Run all tests.