-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Irregular inflector behavior #110
Comments
I'm hoping my issue is related. Here's a failed attempt to pluralize inflector.irregular('human', 'humans');
console.log(inflector.pluralize('human')); // --> "humen" |
I'm having a similar issue but with Example.
expected behavior This is causing an issue when I do the following this.store.query('bolo-setting', { org_id: 1 }); which results in the following error message
Removing the Uncountable rule corrects the issue for the I discovered this issue when updating to Ember-CLI 2.9.0 from Ember-CLI 1.13.13 and removing the Ember inflector per the deprecations |
Yep, same issue here. import Inflector from 'ember-inflector';
export function initialize() {
Inflector.inflector.irregular('human', 'humans'); // FIXME:
}
export default {
name: 'inflectors',
initialize
}; On backend: ActiveSupport::Inflector.inflections do |inflect|
inflect.irregular 'human', 'humans'
end |
Is this an inconsistency between this repo and Rails inflector API? If not, then it's better to use the API to make your own adjustments. The goal of this project is to provide a base-set that mirrors Rails inflector API. |
Hello there,
I have these rules (among others) in my app.
With this config I get this result:
It seems the second irregular rule is never met, this line looks like the culprit. It checks for the end of the rule, so, strings ending the same way can respond wrongly.
Another thing I notice is that this code makes the irregular declaration order specific. If I invert the order like so:
I get the right result:
Can we make the irregulars check for the whole expression first?
The text was updated successfully, but these errors were encountered: