stfcodes / ember-do-forms Goto Github PK

The do-fields component would allow the usage of do-form subcomponents with the do-form semantics and without the form logic.

After updating our application from ember 3.5 to 3.8 many of our component integration tests started failing Assertion Failed: You cannot specify both a positional param (at position 0) and the hash argument 'controlType'. After looking into it, I discovered the one thing those components had in common was that they use ember-do-form components. I still haven't identified any documented relevant changes in Ember itself between 3.5 and 3.8, but the the components in this addon use positional params and also have controlType.

Has anyone successfully used this addon w/ Ember 3.6+?

I have been using this addon for a while now and I have found it very easy to customize to do whatever craven thing our designers come up with.

But I am stumped on this one. I have a custom validator (ember-cp-validations) that validates that the username the user typed is available and returns a message with an alternative suggestion if it is not. I would like that validator to validate eagerly - show the message as you type. I see that the validator is validating eagerly but the dp-feedback component doesn't display the message until you focusOut.

Any suggestions for how to accomplish this? Thanks!

With global and inline configuration this addon supports a variety of css frameworks. Even when something is not supported, it can be relatively easy to extend to support (for example #2).

It would be nice to have theming support out of the box for:

• BS4
• Semantic UI
• Foundation
• BS3
• Others..

Version 3.3.2 of ember-cp-validations just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cp-validations is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

READMEs are great, but interactive example pages are greater.

Currently the code is undocumented and there's a mixture of public / private obscure stuff.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Version 1.3.1 of ember-cli-htmlbars just got published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-htmlbars is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi,
there is problem with displaying object with boolean field through do-control component as it uses and sets value, but for checkbox it should use checked property.

Therefore I have to set up something like:

{{#do-form model submit=(action 'update' model) as |form|}}
   {{#form.do-field 'hasName' as |f|}}
      {{f.do-control 'checkbox' checked=model.hasName}}
...

which is very inconvenient. I wonder if there is a workaround?
Thanks.

It would be nice to be able to also extend the form classes.

For example, Semantic UI error messages only show up if the form itself also has a class of ui form error.

Thanks!

There should be an option to auto-generate the data-test-* attributes for form elements to reduce boilerplate in templates.

This option should default to false for the moment.

Version 4.5.0 of loader.js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Textarea: cols, wrap.

Other controls: form.

Pretty sure others are missing too the minimum should be required