Closed
Bug 1406880
Opened 8 years ago
Closed 7 years ago
Decide where multiline Pattern spans should start
Categories
(L20n :: JS Library, enhancement)
L20n
JS Library
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stas, Assigned: stas)
Details
Bug 1397234 changed how Patterns spans are calculated. Quoting https://github.com/projectfluent/fluent.js/pull/76#issuecomment-333573836:
key = Value
^---- Pattern span start before bug 1397234
key = Value
^---- Pattern span start after bug 1397234
Multiline Patterns were changed as follows (the Github comment has it wrong):
key =
^---- Pattern span start before bug 1397234
Value
key =
Value
^---- Pattern span start after bug 1397234
I'm not sure if that's good or bad. Should the Patterns start at the first meaningful character instead? Like so:
key =
Value
^---- Pattern span start after bug 1397234
Comment 1•8 years ago
|
||
My intuitive guess would be that we want to do what you suggest in your last snippet - since we remove leading white spaces, we should start the span on the first non-white character of the value.
Comment 2•8 years ago
|
||
Same here, last snippet.
| Assignee | ||
Comment 3•7 years ago
|
||
This was fixed in passing by https://github.com/projectfluent/fluent.js/commit/4d1a41fb7e21af01d582e36b29bc8e20ee731dba.
Assignee: nobody → stas
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•