Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

Reserve locale and htmlSafe attributes #381

Merged
merged 1 commit into from
Jul 5, 2016

Conversation

jasonmit
Copy link
Contributor

@jasonmit jasonmit commented Jun 28, 2016

Based on our discussion over slack /cc @jamesarosen

This is for handling deprecations ahead of 5.x

Loosely related to #377

@jasonmit jasonmit force-pushed the reserve-locale-htmlSafe branch from b1835da to 1db3ff2 Compare June 28, 2016 20:08
service.t('not.yet.translated', { locale: true });
assert.equal(deprecations, 2);

service.t('not.yet.translated');
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe service.t('not.yet.translated', { some: 'other key' })

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, I'll add one that includes interpolation

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All done, it's on line 63 to catch both w/ and w/o data attribute.

@jasonmit jasonmit force-pushed the reserve-locale-htmlSafe branch from 1db3ff2 to a7bcf7c Compare June 29, 2016 00:08
@jamesarosen
Copy link
Owner

+1

@jasonmit
Copy link
Contributor Author

jasonmit commented Jul 3, 2016

@jamesarosen once merged I'll start on the second part of what we discussed, supporting inlining a locale when looking up a translation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants