[Studio] Dynamic Resolvers#637
Draft
markus-moser wants to merge 30 commits into
Draft
Conversation
…rategy Selecting the attribute loading strategy before choosing a data object class fired the load-class-attributes request with an empty classId.
The resolver registry shares a single id namespace across all four groups; bare ids like 'id' or 'attribute' are collision-prone once third parties register or override types.
Restores the bundle's ESLint style (standard-with-typescript) across all files touched by the refactoring, adds the explicit return types the config requires, and rebuilds the module registration in index.tsx on top of the original formatting to stay within the max-lines limit.
markus-moser
force-pushed
the
feature/dynamic-resolvers-improvements
branch
from
aa31662 to
8d3e789
Compare
|
This file contains hidden or 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
3 participants
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.
Changes in this pull request
Supersedes #635 by @rjjackson22 (TorqIT).
Refactors the Studio resolver step to the dynamic-type registry pattern, so resolver strategies can be added or overridden by other bundles.
Fixes on top of #635:
loading.*,createLocation.*, …) to avoid collisions in the shared registrymax-linesviolation inindex.tsx