Changelog for 0.3.0 - #2
Merged
Merged
Conversation
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
1 participant
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.
Adds the
0.3.0entry, and backfills0.2.0, which shipped without one.0.3.0is the quadratic-scanning fix from #1. It is a minor rather than a patch because the performance characteristic it changes is the reason to take it, but the public API and the output are both unchanged — all 31 storefront locale files of a production Shopify theme round-trip byte-identically before and after.Note for whoever reads the links at the bottom: the existing
0.1.0link points atreleases/tag/v0.1.0, but the tags in this repo carry novprefix, so that link is broken. The two new ones use the real tag names. Left the old line alone rather than fix it as a drive-by.