> Let's talk about how to get there? The changes you propose seem to cover: - Localization API (https://github.com/projectfluent/fluent.js/tree/master/fluent-dom) - CachedIterable (https://github.com/projectfluent/cached-iterable) - L10nRegistry And in result - fluent-react (https://github.com/projectfluent/fluent.js/tree/master/fluent-react) - fluent-rs (https://github.com/projectfluent/fluent.js/tree/master/fluent-react) I have a lot of questions about your proposal. I don't understand what signature of methods on Localization do you propose, how such object that builds in the cache should look like, etc. But the bottom line is that if I'm not mistaken, this patch can land and enable me now, while we work on the proposed refactor. We're one r+ away from enabling removal of DTD on the startup path. Do you believe we should block that on your proposed changes?
Bug 1558602 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Let's talk about how to get there? The changes you propose seem to cover: - Localization API (https://github.com/projectfluent/fluent.js/tree/master/fluent-dom) - CachedIterable (https://github.com/projectfluent/cached-iterable) - L10nRegistry And in result - fluent-react (https://github.com/projectfluent/fluent.js/tree/master/fluent-react) - fluent-rs (https://github.com/projectfluent/fluent-rs) I have a lot of questions about your proposal. I don't understand what signature of methods on Localization do you propose, how such object that builds in the cache should look like, etc. But the bottom line is that if I'm not mistaken, this patch can land and enable me now, while we work on the proposed refactor. We're one r+ away from enabling removal of DTD on the startup path. Do you believe we should block that on your proposed changes?