feat: enable Jekyll-compatible dot notation in assign tags - #120
Merged
Conversation
This was referenced Feb 28, 2026
osteele
force-pushed
the
fix-60-assign-dot
branch
from
August 12, 2026 16:25
5615794 to
ae63630
Compare
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.
Summary
assigntags (e.g.,{% assign my_obj.prop = "value" %})Closes #60
Details
The liquid v1.8.0 release adds
EnableJekyllExtensions()which supports dot notation on the left-hand side of assign statements. This is now enabled by default in gojekyll's liquid engine.Note: Ruby Jekyll does not actually support
{% assign page.canonical_url = page.url %}(assigning to thepagedrop's properties). This works for custom variables but thepagedrop remains read-only, matching Jekyll's behavior.Test plan