-
Notifications
You must be signed in to change notification settings - Fork 21
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
form component #136
Labels
Comments
created corresponding branch with a simple default implementation. the implementation is based on the use of vue form generator - sample form:
remaining tasks:
vfg docs: https://vue-generators.gitbook.io/vue-generators/fields |
Closed
smcgrath0
added a commit
that referenced
this issue
Aug 24, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 24, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 24, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 24, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 24, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 25, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 25, 2020
smcgrath0
added a commit
that referenced
this issue
Aug 25, 2020
smcgrath0
added a commit
that referenced
this issue
Sep 4, 2020
Closed
qial
added a commit
that referenced
this issue
Sep 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the problem.
websites often have forms. We should be able to use oue json schema format or a more direct vue-form-generator form definition to render a form on a website with a defined target for the form action (ajax post request to specified URL).
We should be careful to evaluate overall page speed when enabling a form feature on a public facing website and evaluate how we'd like to tie in forms with objects and headwirecom/peregrine-cms#374
The text was updated successfully, but these errors were encountered: