Service is able to accept any value in the token pattern of {} but the component is limited to numbers. #6

notmessenger · 2014-11-26T03:46:44Z

Consider making the format being used configurable

Possibly relates to #9

juwara0 · 2015-11-25T14:41:51Z

I am working on this

notmessenger added the enhancement label Nov 26, 2014

notmessenger mentioned this issue Nov 26, 2014

Evaluate how Ember functions for translation and localization support can be leveraged #9

Open

notmessenger added 0 - Backlog and removed 1 - Ready labels Jun 12, 2015

notmessenger added this to the v1.11.0 milestone Aug 4, 2015

notmessenger removed the 0 - Backlog label Sep 24, 2015

notmessenger mentioned this issue Oct 13, 2015

Deprecation warning: You modified translatedString twice in a single render. This was unreliable in Ember 1.x and will be removed in Ember 2.0 #200

Merged

notmessenger assigned juwara0 Nov 25, 2015

notmessenger added the in progress label Nov 25, 2015

juwara0 added a commit to juwara0/sl-ember-translate that referenced this issue Dec 1, 2015

Closes softlayer#6

be9f3aa

juwara0 mentioned this issue Dec 1, 2015

Improved Token Pattern to allow alphanumeric #223

Merged

notmessenger closed this as completed in #223 Dec 3, 2015

notmessenger removed the in progress label Dec 3, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Service is able to accept any value in the token pattern of {} but the component is limited to numbers. #6

Service is able to accept any value in the token pattern of {} but the component is limited to numbers. #6

notmessenger commented Nov 26, 2014

juwara0 commented Nov 25, 2015

Service is able to accept any value in the token pattern of {} but the component is limited to numbers. #6

Service is able to accept any value in the token pattern of {} but the component is limited to numbers. #6

Comments

notmessenger commented Nov 26, 2014

juwara0 commented Nov 25, 2015