meteor-autoform | Meteor package that adds UI components | Form library
kandi X-RAY | meteor-autoform Summary
kandi X-RAY | meteor-autoform Summary
AutoForm is a Meteor package that adds UI components and helpers to easily create basic forms with automatic insert and update events, and automatic reactive validation.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Gets the key for the given element .
meteor-autoform Key Features
meteor-autoform Examples and Code Snippets
Community Discussions
Trending Discussions on meteor-autoform
QUESTION
I am engineering a custom autocomplete
type for the afQuickfield
in my Meteor project. The issue I am having is that when I set the type="autocomplete"
on the afQuickfield
, the class="form-control"
attribute is missing. For all other field types, it is included.
I grepped form-control
across the entire codebases for meteor-autoform
as well as the scss
and js
directories of the bootstrap
library. I only see occurances in the changelog and class definitions in scss/css.
I could just include class="form-control"
in the afQuickfield
definition, but that's a monkey patch and I'm not a fan of cutting corners.
Can anyone help me understand how form-control
gets assigned in autoForm
fields?
Here's my custom autocomplete
code (it's a WIP, so no judging!). I'm just hoping to start with a text element with the proper atts
so I can build from there.
ANSWER
Answered 2020-Dec-15 at 13:41Actually this seems to be a follow-up bug from AutoForm
, because it should already throw the following error, when including afInputText
:
What about the missingThere are multiple templates named 'afInputText'. Each template needs a unique name
form-control
?
This is correct in itself, because there is no class
attribute on the input
within the afAutoComplete
template.
AutoForm built-in input types have no class attributes, because they will be overridden by the themes.
For example the text
input in the Bootstrap 4 theme looks currently like this:
QUESTION
In our Meteor v1.11.1
application, we are using Bootstrap 3, aldeed:autoform@6.3.0
, and aldeed:collection2@3.2.1
in blaze to validate forms. We really want to implement the "least-custom" solution to display and validate our form inputs.
We can't wrap our heads around why even the most basic error message doesn't appear in the form when we submit? We narrowed the form down to one field and a submit. The HTML elements are in the DOM, but no hint of messaging appears upon validation.
The schema for the form is:
...ANSWER
Answered 2020-Dec-04 at 08:19The issue comes from the missing Tracker
that is required in order to generate reactive validation messages:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install meteor-autoform
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page