-
Notifications
You must be signed in to change notification settings - Fork 33
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
Constant used in template is not parsed properly #129
Comments
Thanks! Yes, your diagnosis seems correct to me, a PR would be great! (Or I could fix it myself if you no longer have time, since my answer is a week late). |
I can do it. I've been using a fixed version in my project. I just need to write some tests to open the PR. |
kaj
added a commit
that referenced
this issue
Jul 22, 2023
* Added a check that no more than one of the http-types, mime02, or mime03 features are enabled (PR #124). Thanks @rustafarian-dev. * Changed the writer type from `W: &mut Write` to just `W: Write` (PR #125). Thanks @kornelski! * Fixed handling of `MULTI_WORD_CONSTANTS` in templates (Issue #129, PR #130). Thanks @wezm! * More ways to create a working rust symbol name from a "strange" static file name. Illegal characters are replaced by `_`, and if the file name starts with a number it is prefixed with `n` (Issue #82, PR #132). Thanks @Aedius for reporting! * Fixed more clippy lints (PR #123, #127). Thanks @vbrandl! * Updated `rsass` to 0.28.0 and `itertools` to 0.11.0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a constant:
Which I import and use in a template like:
This results in generated code:
I think the issue might be the second part of
rust_name
does not include uppercase letters. I tried adding them and it fixed the problem. I can submit a PR with the changes if you like.ructe/src/expression.rs
Lines 54 to 62 in 4065b75
The text was updated successfully, but these errors were encountered: