7 Commits

Include renames

Author	SHA1	Message	Date
Charles-P. Clermont	c9ae128354	Rename Parser#expression_node -> Parser#expression	2026-01-26 16:52:17 -05:00
Charles-P. Clermont	7d0bdd166d	Move parse_expression to Parser.unsafe_parse_expression ... - Add Parser#string - Add Parser#unsafe_parse_expression - Add private Parser#parse_expression - Remove ParseContext.parse_expression - Remove Tag.parse_expression - Condition.parse_expression now takes a parser as argument	2026-01-26 16:52:17 -05:00
Charles-P. Clermont	cf3d845315	Move safe_parse_expression into Parser.expression_node ... - Make `Parser` accept the expression cache - Remove `safe_parse_expression` from `ParseContext` - Replace all usage of `safe_parse_expression` with `parser.expression_node`	2026-01-26 16:52:17 -05:00
Charles-P. Clermont	62400f71d0	Remove :error_mode	2026-01-14 09:55:20 -05:00
Charles-P. Clermont	d936ce4ac9	Remove :lax, :strict and :warn error modes	2026-01-14 09:54:19 -05:00
Guilherme CarreiroandGitHub	32b50ecafe	Bump Liquid to 5.11.0 (#2012) ... This commit reverts the Inline Snippets tag (#2001) and bumps Liquid to 5.11. For now, the inclusion of Inline Snippets in the latest Liquid release is being treated as a bug. While #2001 does implement the scope contained in RFC#1916, we need to take a step back to make sure we’re setting our sights high enough with this feature, and that we’re truly supporting theme developers in the ways they need. If you have any feedback, please leave a comment on RFC#1916. - Liquid Developer Tools	2025-11-19 18:03:23 +01:00
Guilherme CarreiroandGuilherme Carreiro	738540a601	Update infrastructure that handles parsing switching: ... * Remove development helpers from parse context * Simplify strict_parse_with_error_mode_fallback and update documentation * Add unit tests for `Liquid::Expression` and `Liquid::ParseContext` * Update test helpers to work better with the `:rigid` mode	2025-10-27 16:33:31 +01:00