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

Support "proxy" element #172

Open
timriley opened this issue Apr 1, 2019 · 0 comments
Open

Support "proxy" element #172

timriley opened this issue Apr 1, 2019 · 0 comments

Comments

@timriley
Copy link
Contributor

timriley commented Apr 1, 2019

Make it possible to e.g. have a standard-rendered form but with a place we can hook in some custom markup (e.g. for a custom-built field or similar). This would make it possible to continue to use formalist for forms that do require some customisation.

I'd see it working something like this...

In the form definition:

proxy :my_custom_field

In the markup, somewhere on the same page as where the form rendering is happening:

<div data-formalist-proxy="my_custom_field">
  <!-- ALL THE CUSTOM MARKUP HERE -->
</div>

The formalist renderer would know to look for this and insert it into the right place on the form.

The challenge here would be working out a way to get the actual data for the element into that custom markup. @makenosound — do you have any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant