Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial commit for issue WEB-7671 Allow Handlebars/Mustache expression delimiters to be changed from the defaults #935

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

SammoMichael
Copy link

Trying to finish this enhancement as it it would help very many companies and teams i (including mine)

As it is normal practice to use a custom delimiter for "first pass" hydration and reserve "{{ }}" mustache templates for second pass. Also people have requested "{% %}". This PR will allow one or more custom delimiters to be used and no longer considered error in the file they are embedded in

@piotrtomiak piotrtomiak self-assigned this Jan 21, 2025
@piotrtomiak
Copy link
Contributor

Hi! Thanks for the contribution! It looks like the part to enable parsing with the new delimiters is not yet done. Are you planning to working on this?

@SammoMichael
Copy link
Author

Hi! Thanks for the contribution! It looks like the part to enable parsing with the new delimiters is not yet done. Are you planning to working on this?

Hello Piotr yes I will try to finish the lexer and parser part, my main obstacle is I have been struggling to test the changes I make. Every time I build the plugin doesn't get installed in the sandbox IDE and when i try to install manually I get "bad file descriptor" error.

Either way I will try to finish this as I have another internal plugin I developed for my company that would really benefit from these changes which bundles this Handlebars/Mustache under the hood.

@SammoMichael
Copy link
Author

SammoMichael commented Jan 23, 2025 via email

@piotrtomiak
Copy link
Contributor

piotrtomiak commented Jan 24, 2025

@SammoMichael - I am looking into the problem. It looks like the Gradle setup has degraded to the level it requires a lot of work. I'll let you know once I fix it, but it's gonna be on Monday at earliest.

@piotrtomiak
Copy link
Contributor

@SammoMichael - I've finally managed to fix the setup, sorry that it took so long. To be able to develop the change, you should switch to 243 branch and develop the fix for that branch. On master branch, the code is sometimes behind the released platform, and you might not be able to compile it. Once the fix is ready, I will apply it to the master branch.

@SammoMichael
Copy link
Author

SammoMichael commented Jan 28, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants