Add macros (discussion, do not merge) #204
Closed
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.
In order to add auto data storage (#157), we need macros to generate form fields. This is because the code to populate field values with data the user has entered is complex. I don't think users of the kit will find it easy to write that code for each field.
Macros also help us make prototypes accessible, again without our users having to learn that HTML.
I think we should try and keep each macro as simple as possible as an MVP.
This PR is for discussion, for example is
macro.
the right naming convention? Should allowing users to easily add their own macros be part of this PR?Example of usage: