[pull] master from harttle:master #7
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
340564e to
b5b2a98
Compare
b1e4c1d to
371da3d
Compare
BREAKING CHANGE: `ownPropertyOnly` default value changed to `true`
BREAKING CHANGE: main entry need Node.js>=14 to run, you can build LiquidJS by your own by using ESM entry.
BREAKING CHANGE: `evalToken` now returns a generator (LiquidJS async), which is different from `evalToken` in previous LiquidJS versions.
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.0.4 to 3.1.2. - [Release notes](https://github.com/isaacs/minimatch/releases) - [Commits](isaacs/minimatch@v3.0.4...v3.1.2) --- updated-dependencies: - dependency-name: minimatch dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
# [10.0.0](v9.43.0...v10.0.0) (2022-11-27) ### chore * rename filters to snake style, [#487](#487) ([ff112a4](ff112a4)) ### Code Refactoring * `_evalToken` renamed to `evalToken` ([4e1a30a](4e1a30a)) * change `ownPropertyOnly` default value to `true` ([7eb6216](7eb6216)) * delay creation of `operatorsTrie` and hide this implementation ([bb58d3e](bb58d3e)) * remove `toThenable` export ([ffefd91](ffefd91)) * remove use of internal `Context` class in `evalValue` argument ([b115077](b115077)) ### Performance Improvements * target Node.js 14 for cjs bundle (main entry) ([1f6ce7c](1f6ce7c)) ### BREAKING CHANGES * `evalToken` now returns a generator (LiquidJS async), which is different from `evalToken` in previous LiquidJS versions. * main entry need Node.js>=14 to run, you can build LiquidJS by your own by using ESM entry. * `ownPropertyOnly` default value changed to `true` * `<liquidjs>.toThenable` is removed, use `<liquidjs>.toPromise` instead * `evalValue` won't support `Context` as second argument anymore. * use `operators` instead of `operatorsTrie` as Tokenizer constructor argument, #500 * keys in `<liquidjs>.filters` are now in snake case (instead of camel case), identical to that in Liquid template.
# [10.1.0](v10.0.0...v10.1.0) (2022-11-29) ### Features * timezone name for `opts.timezoneOffset` and `date` argument, fixes [#553](#553) ([89c6c76](89c6c76))
Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. - [Release notes](https://github.com/SamVerschueren/decode-uri-component/releases) - [Commits](SamVerschueren/decode-uri-component@v0.2.0...v0.2.2) --- updated-dependencies: - dependency-name: decode-uri-component dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. - [Release notes](https://github.com/SamVerschueren/decode-uri-component/releases) - [Commits](SamVerschueren/decode-uri-component@v0.2.0...v0.2.2) --- updated-dependencies: - dependency-name: decode-uri-component dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
* feat: static variable analysis * Accept any iterable from `children`, `arguments`, etc. * Test analysis of standard tags * Use `TagToken.tokenizer` instead of creating a new one * Test analysis of netsted tags * Group variables by their root value * Test analysis of nested globals and locals * Analyze included and rendered templates WIP * Use existing tokeni 8000 zer when constructing `Hash` * Improve test coverage * Analyze variables from `layout` and `block` tags * Test analysis of Jekyll style includes * Handle variables that start with a nested variable * Async analysis * Test non-standard tag end to end * Implement convenience analysis methods on the `Liquid` class * More analysis convenience methods * Accept string or template array * Draft static analysis docs * Deduplicate variables names * Fix isolated scope global variable map * Coerce variables to strings instead of extending String * Private map instead of extending Map * Fix e2e test * Tentatively implement analysis of aliased variables * Fix nested variable segments array * Update docs sidebar
## [10.20.1](v10.20.0...v10.20.1) (2025-01-04) ### Bug Fixes * break/continue stops whole template, [#783](#783) ([5f1a4cf](5f1a4cf)) * enumerate plain objects in where/where_exp, [#785](#785) ([#788](#788)) ([25ef104](25ef104)) * preserveTimezones support for RFC2822 date, [#784](#784) ([59cf3c0](59cf3c0))
## [10.20.3](v10.20.2...v10.20.3) (2025-02-09) ### Bug Fixes * empty tagToken.args since 10.20.0, fixes [#796](#796) ([38a0f51](38a0f51))
* feat: add find_index, has, and reject filters * Minor tweaks * Change semantics of jekyllStyle, add more tests * Some docs improvements
# [10.21.0](v10.20.3...v10.21.0) (2025-02-23) ### Features * add find_index, has, and reject filters ([#799](#799)) ([0deb93e](0deb93e))
Improve documentation
Replaced square brackets with round ones in a link markup.
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
Looks like just a typo.
DISCLAIMER: This may not be the proper way to approach the issue.
Although the Markdown code is proper, on the website itself it is incorrectly rendered as "{{` and `}}".
The reason for the disclaimer above is that I’m imagining this may be an issue at the content rendering level, and my fix here is just a workaround of that issue. — Given this, I’ll not be offended if this PR of mine is rejected and closed. 🙂
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot]. Want to support this open source service? Please star it : )