-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Replace ember-validations #1382
Comments
@martndemus can you comment on what state |
We are not planning to do anything about ember-validations. |
@martndemus thanks for the info. |
Well, it seems to be a large piece of work, migrating it. I've started the new branch but the process is not so straightforward. See https://github.com/HospitalRun/hospitalrun-frontend/compare/ember-validations?expand=1 The most important problems are:
To sum up, maybe forking would be a good quick solution. |
@stukalin - What would be the best approach to forking this? Should someone who have repository creation permissions fork it to the Hospital Run Repo? It's probably better than running it off someone's personal fork. |
That'd be the best option. I don't have sufficient right, I've just verified that. @jglovier, could you help forking the https://github.com/DockYard/ember-validations to our repo? |
Done. See: https://github.com/HospitalRun/ember-validations Thanks folks!! ❤️ 🙇 ✨ |
So now it's only matter of applying the fix mentioned in the very first message to our fork and reference it from the main app. |
I'm going to try to get that done this morning (well, morning East Coast US). |
ember-validations
is no longer under active development, and has become a blocker for completion of #1370 (ember-getowner-polyfill.import deprecation). There's a PR that's over a year old that is unlikely to ever be accepted: DavyJonesLocker/ember-validations#442.The way I see it there are two options: fork or replace.
If fork, it's possible that forking and cherry-picking the commit from that PR will solve the immediate problem.
If replace, the two most common actively developed validation solutions to my knowledge are ember-cp-validations and ember-changeset-validations. I recommend ember-cp-validations for the following reasons:
The text was updated successfully, but these errors were encountered: