liquid

Here is an example:
https://github.com/BuilderIO/mitosis/pull/266/files#diff-d77df8a4086c893b4cd3954952a7598b6f85dcab3ef5f5a7116c30ba589b467eL13

If we import a function like this:

import { getMitosisConfig } from 'src/helpers/get-mitosis-config';

TS and our local env & CI won't complain.

However, our production build will actually break. We need the import to be a rel

I want to animate the layout with similar animation but from bottom to top. How can I achieve this animation.

Sorry for posting this question in the issue.

It will be very helpful if you guide me to solve the problem.

Example test case:

#[test]
#[should_panic]
fn test_recursively_included_template_does_not_produce_endless_loop() {
    panic!("We don't check recursion depth");
    /*
    let parser = liquid::ParserBuilder::with_liquid().include_source(Box::new(InfiniteFileSystem)).build();
    parser.parse("{% include 'loop' %}").unwrap();
    */
}

We probably want Parser to have an `

A lot of developers still use the old method of hardcoding various Shopify routes.

Given there's a fairly small amount of routes, could a check be included to ensure liquid routes are being used?

<form action="{{ routes.search_url }}">...</form>

Vs.
<form action="/s

Add benchmarks.

These could be translated into Markdown from the test files in https://github.com/SlinSo/goTemplateBenchmark.

There might also be benchmarks or test files in some of the other Liquid implementations.