Headers aren't properly rendering.

The checkbox component and others need to have the readonly attribute implemented.

Adapt our existing data structure to support https://github.com/offirgolan/ember-cp-validations

#285 introduced the ability for Foxy Form to self-identify required fields eliminating the need to have @required={{true}} in the template code.

However, @required is still needed for Foxy Forms to set the 'required' class, which is needed for CSS purposes, ie:

.form-for .field-for.required > label::after {
  content: "*";
  color: #e93c3c;
}

Hi, i like the ember-foxy-forms.

But I have some doubts to make the add-on works in some projects.
For example:

• Translations (Buttons like submit)
• html customizations in fields... Like put HTML validations
• HTML5 validations.
• Support for existing validator for ember.
• Ways to load the options from Ember Data promise. Customizing the options using some attribute by name.

My use case is, an form using Ember Data and Ember Octane with Glimmer.
In that scenario I want to pass an "Ember.store.find" promise to the template using component tracked attribute.
And use the tracked attribute with Ember Store find promise as combo select options, instead use simple hash.

Could someone help me with that? I tried many many other form add-ons but can't do that things.
@joegaudet @abeforgit

Thanks.

as a developer
in order to apply custom field and form styles
I need ember-form-for to support a configuration setting that allows for defining form-for field-for settings.

ac:

• Configuration params that are applied to both the form-for and field-for components in their class definitions.

A standard form use case is an action less button, extend that.