{{ message }}
Fix typescript types in DOMLocalization#643
Merged
Merged
Conversation
Contributor
Author
eemeli
approved these changes
Jul 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I noticed some types were not good enough when I started checking the types in firefox' lit-utils file, for example in these lines: https://searchfox.org/mozilla-central/rev/a9e77c69ed8a2b408bbe64553316c7849ec3d267/toolkit/content/widgets/lit-utils.mjs#160,179
Indeed in Lit we're dealing with DocumentFragments more. This works fine in Fluent, only the types aren't correct.