fix: Send factory as string in SchemaWidget and filter field types in types control panel#7930
Open
Shyam-Raghuwanshi wants to merge 1 commit intoplone:mainfrom
Open
Conversation
… types control panel
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.
When adding a new field in the dexterity types schema editor (/controlpanel/dexterity-types//schema), the field factory was sent to the backend as an object (e.g. {value: "label_text_field", label: "Text"}) instead of a plain string, causing a "missing parameter factory" error. Additionally, form-only field types (like static_text, hidden, radio_group) were shown in the field type dropdown even though they don't have corresponding Plone field factories on the backend.
Ref: plone/plone.restapi#1969