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

Export Formio Typescript types #2

Closed
29 tasks done
sergei-maertens opened this issue May 15, 2023 · 1 comment · Fixed by #14, #15, #16, #17 or #18
Closed
29 tasks done

Export Formio Typescript types #2

sergei-maertens opened this issue May 15, 2023 · 1 comment · Fixed by #14, #15, #16, #17 or #18
Assignees

Comments

@sergei-maertens
Copy link
Member

sergei-maertens commented May 15, 2023

TODO:

  • TextField
  • Email
  • Date
  • Datetime
  • Time
  • Phone number
  • Postal code (it's a textfield so probably not needed?)
  • File upload
  • Textarea
  • Number
  • Checkbox
  • Checkboxes
  • Select
  • Currency
  • Radio
  • IBAN
  • License plate
  • BSN
  • FamilyMembers
  • Signature
  • Co-sign
  • Co-sign-old
  • Map
  • Editgrid (repeating groups)
  • Content
  • Columns
  • Fieldset
  • Postcal code (custom)
  • Password
@sergei-maertens sergei-maertens self-assigned this May 15, 2023
@sergei-maertens sergei-maertens converted this from a draft issue May 15, 2023
@sergei-maertens sergei-maertens moved this from Todo to In Progress in Development May 15, 2023
This was referenced May 16, 2023
sergei-maertens added a commit that referenced this issue Jun 6, 2023
✅ [#2] -- make number input properly multiple capable
sergei-maertens added a commit that referenced this issue Jun 6, 2023
✨ [#2] -- define types for date component
sergei-maertens added a commit that referenced this issue Jun 6, 2023
This strips out most of the super-type schema properties, as they are
not relevant for the content component.
sergei-maertens added a commit that referenced this issue Jun 6, 2023
✨ [#2] -- implement type definition for content component
@sergei-maertens sergei-maertens moved this from In Progress to Todo in Development Jun 15, 2023
@sergei-maertens sergei-maertens moved this from Todo to In Progress in Development Aug 25, 2023
@sergei-maertens sergei-maertens moved this from In Progress to Todo in Development Aug 28, 2023
@sergei-maertens sergei-maertens moved this from Todo to In Progress in Development Sep 5, 2023
sergei-maertens added a commit that referenced this issue Oct 10, 2023
Note that the current implementation puts minTime and maxTime in the
root rather than nested in the validate object, which is something
that will have to change.
@github-project-automation github-project-automation bot moved this from In Progress to Done in Development Oct 16, 2023
@github-project-automation github-project-automation bot moved this from Done to In Progress in Development Oct 16, 2023
sergei-maertens added a commit that referenced this issue Dec 4, 2023
This one is a bit special because we're modelling the current situation
and some clean up is probably in order, notably:

* validation tab doesn't support error messages
* validation tab doesn't support validator plugins
* button texts are not wired up to be translatable (
  fixed in this type definition at least)
* missing controls to include field in PDF/email/confirmation
  page etc., so now it's only hidden if all child components
  are hidden.

The value type can also not be defined statically, because this
is a container component that depends on the runtime child
components, which in turn dictate the value type of a repeating
group itself.
@github-project-automation github-project-automation bot moved this from In Progress to Done in Development Dec 4, 2023
sergei-maertens added a commit that referenced this issue Dec 4, 2023
This one is a bit special because we're modelling the current situation
and some clean up is probably in order, notably:

* validation tab doesn't support error messages
* validation tab doesn't support validator plugins
* button texts are not wired up to be translatable (
  fixed in this type definition at least)
* missing controls to include field in PDF/email/confirmation
  page etc., so now it's only hidden if all child components
  are hidden.

The value type can also not be defined statically, because this
is a container component that depends on the runtime child
components, which in turn dictate the value type of a repeating
group itself.
@github-project-automation github-project-automation bot moved this from Done to In Progress in Development Dec 4, 2023
sergei-maertens added a commit that referenced this issue Dec 5, 2023
This snuck in accidentally because the component inherits from the
email component in the implementation, but it was not a conscious
decision.

This does *not* make it impossible to send the data to StUF-ZDS, ZGW
APIs or Objects API integration as the unmapped data is included by
default in some form anyway or there are existing mechanisms to
include it via custom data templates.
@sergei-maertens sergei-maertens moved this from In Progress to Implemented in Development Dec 5, 2023
@github-project-automation github-project-automation bot moved this from Implemented to Done in Development Dec 7, 2023
sergei-maertens added a commit that referenced this issue Dec 7, 2023
This snuck in accidentally because the component inherits from the
email component in the implementation, but it was not a conscious
decision.

This does *not* make it impossible to send the data to StUF-ZDS, ZGW
APIs or Objects API integration as the unmapped data is included by
default in some form anyway or there are existing mechanisms to
include it via custom data templates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment