Closed
Bug 1320060
Opened 8 years ago
Closed 7 years ago
l20n.migrate.transforms.* should take FTL.Patterns as arguments
Categories
(Localization Infrastructure and Tools :: Fluent Migration, defect)
Localization Infrastructure and Tools
Fluent Migration
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: stas, Unassigned)
References
Details
We should decide what we want all transforms to evaluate to, and what arguments they take. Right now transforms take strings and return Patterns. By making them take Patterns and return Patterns we'll allow FTL to FTL migrations.
Reporter | ||
Updated•7 years ago
|
Blocks: fluent.migrate
Reporter | ||
Comment 1•7 years ago
|
||
This is out of the scope of any of the milestone in the L20n in Gecko Landing Plan. Closing as WONTFIX.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Reporter | ||
Updated•6 years ago
|
No longer blocks: fluent.migrate
Component: Python Library → Fluent Migration
Product: L20n → Localization Infrastructure and Tools
You need to log in
before you can comment on or make changes to this bug.
Description
•