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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - Implement
String.prototype.toLocaleUpper/LowerCase
#2822[Merged by Bors] - Implement
String.prototype.toLocaleUpper/LowerCase
#2822Changes from all commits
ed17f5b
008d85b
1a9c79c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way that we can avoid putting large binary data into git history? maybe generating this in a
build.rs
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We started with the build.rs approach on this, but it did increase compile times to much, especially in the ci. I think for now this should work. Alternativeley, we could move
boa_icu_provider
to a separate repository to make this easier on the git history.Also, before looking at the size of this file, I think we should probably look at the 262 test result files on the
gh-pages
branch :DThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We started with the build.rs approach on this, but it did increase compile times to much, especially in the ci. I think for now this should work. Alternativeley, we could move boa_icu_provider to a separate repository to make this easier on the git history.
Yes, for the long term this seems like the a good solution.
😆 Yeah, It's big, but we could always edit the history on the
gh-pages
thoThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this file doesn't change much, we might want to use git LFS: https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage