Field Type Registry: Share custom types across instances#34
Open
nicolas-jaussaud wants to merge 1 commit into
Open
Field Type Registry: Share custom types across instances#34nicolas-jaussaud wants to merge 1 commit into
nicolas-jaussaud wants to merge 1 commit into
Conversation
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
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.
Hi @zinigor!
I believe there is a small issue with the custom field types registration currently
According to this example from the documentation,
FieldTypeRegistryinstances should share custom types:However, it does not seem to be the case currently as each instance hold its own types (here)
This behavior prevents the use of custom fields, as
DataViewinstantiate its ownFieldTypeRegistryinstance (here, inside the constructor) which will trigger a fatal error when reaching this part if a field type is not registeredI switched types to a static attribute, as it seems to be the expected behavior and was the easiest way to fix the issue without introducing syntax changes
If you don't want to change
FieldTypeRegistry, I can also change this PR to pass aFieldTypeRegistryinstance as a second (and optional) parameter ofDataView: