Rust's raw identifiers in variable access

[kellytk]

From the documentation:

You can use a dot (.) to access variable's attributes or methods.

{% match f.fieldtype() %} runs as expected, however {% match f.r#type() %} generates an error unable to parse template.

[vallentin]

Can you check using the main branch? This might have been fixed in #476

[kellytk]

It generates an error problems parsing template source at row y, column x near: "#type() %}...".

[vallentin]

If you're using the main branch. Then try using just {% match f.type() %}. Askama does not support raw identifiers, but the previously mentioned PR implements, so the generator automatically maps e.g. type to r#type, when it generates Rust code for the template.

[kellytk]

With that code the error is expected identifier, found keyword 'type'.

rustc --version 1.57 nightly 2021-9-12

[djc]

It looks like #476 didn't cover the method call scenario (it did not add a normalize_identifier() call in visit_method_call()). Would be great if someone can submit a PR (ideally including a test case).

[kellytk]

@djc In the course of attempting to create a PR, I've cloned the askama repo locally and updated my project's Cargo.toml to resolve the dependency via path to the local repo.

Although I can build the local askama repo, building my project fails with an error failed to get 'askama' as a dependency of package ... and continues to mention virtual manifests. How please can I resolve that?

[Kijewski]

The project consists of multiple crates, and you need to add the path to the crate itself, not the project root. E.g. { path = "/home/kellytk/git/askama/askama" } instead of { path = "/home/kellytk/git/askama" }.

[kellytk]

Which existing test is most like what you'd envision here @djc? I'll attempt to adapt it.