Skip to content
New issue

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

Updating the email and StUF-ZDS inline forms #4686

Closed
robinmolen opened this issue Sep 19, 2024 · 0 comments · Fixed by #4742
Closed

Updating the email and StUF-ZDS inline forms #4686

robinmolen opened this issue Sep 19, 2024 · 0 comments · Fixed by #4742

Comments

@robinmolen
Copy link
Contributor

Thema / Theme

Form designer

Omschrijving / Description

The inline forms for email and StUF-ZDS currently break with the design and use a different form builder (react-json-schema-form). See here: Storybook: Configured Backends

The inline forms should be moved to a modal, like the ZGW api and Object api configuration forms, and make use of Reactjs/Formik instead of react-json-schema-form. This ensures a consistent design and predicable functionality.

Added value / Toegevoegde waarde

Changing the forms frees us from the react-json-schema-form dependency, and helps to keep the UI consistent.

Aanvullende opmerkingen / Additional context

No response

@robinmolen robinmolen added enhancement triage Issue needs to be validated. Remove this label if the issue considered valid. labels Sep 19, 2024
@robinmolen robinmolen self-assigned this Sep 19, 2024
@robinmolen robinmolen changed the title Title here Updating the email and StUF-ZDS inline forms Sep 19, 2024
@joeribekker joeribekker removed the triage Issue needs to be validated. Remove this label if the issue considered valid. label Sep 23, 2024
robinmolen added a commit that referenced this issue Sep 24, 2024
robinmolen added a commit that referenced this issue Sep 25, 2024
robinmolen added a commit that referenced this issue Sep 25, 2024
robinmolen added a commit that referenced this issue Sep 25, 2024
robinmolen added a commit that referenced this issue Sep 25, 2024
robinmolen added a commit that referenced this issue Oct 2, 2024
robinmolen added a commit that referenced this issue Oct 8, 2024
@robinmolen robinmolen linked a pull request Oct 8, 2024 that will close this issue
9 tasks
sergei-maertens added a commit that referenced this issue Oct 31, 2024
Otherwise it would be too easy for form designers to miss the option,
let's make it clear that at least one email address must be entered.
sergei-maertens added a commit that referenced this issue Oct 31, 2024
Similar to the case properties, we can put the payment update mappings
in a separate tab to de-clutter the UI. Next commit will then use
the existing VariableMapping component to manage the actual mappings.
sergei-maertens added a commit that referenced this issue Oct 31, 2024
…ping

Some code repetition, but at least we are now using consistent UI
components for mapping from/to form variables in various places.
sergei-maertens added a commit that referenced this issue Oct 31, 2024
Created a generic component for the button-that-opens-modal with error
icon next to it, which renders the plugin-specific configuration form
inside. This puts the less elegant code in a nice isolated box instead
of spreading across the code base.
@github-project-automation github-project-automation bot moved this from Implemented to Done in Development Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment