We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment, we are not able to commit the webform Field of the KTypes.
webform
This has the reason that the webform is parsed during retrieval and turned into a pydantic model without inheriting the original webform fields.
This pydantic model from the webform then is passed to the related KItem the KType is instanciated for in order to build the custom_properties.
custom_properties
Ideally, this custom_properties model still should hold the original webform so that it can be serialized back to a json when commited.
Hence, the webform Field should be defined through a Pydantic model as well.
The text was updated successfully, but these errors were encountered:
This has been addressed in v3.0.0. The logic with the custom properties and webform has been changed there.
Sorry, something went wrong.
arjungkk
No branches or pull requests
At the moment, we are not able to commit the
webform
Field of the KTypes.This has the reason that the webform is parsed during retrieval and turned into a pydantic model without inheriting the original webform fields.
This pydantic model from the
webform
then is passed to the related KItem the KType is instanciated for in order to build thecustom_properties
.Ideally, this custom_properties model still should hold the original webform so that it can be serialized back to a json when commited.
Hence, the
webform
Field should be defined through a Pydantic model as well.The text was updated successfully, but these errors were encountered: