Nunjucks templates are almost (but not quite) compatible with Jinja.
We wanted to find out if we could adapt existing templates written for Nunjucks so that they would render in Jinja.
Specifically, we wanted to understand what would be involved in making nhs-frontend Nunjucks templates cross-compatible with Jinja.
2024-07-03T11:39:41.2461669Z [2024-07-03 11:39:41,181] ERROR {datahub.ingestion.run.pipeline:491} - Caught error
2024-07-03T11:39:41.2463027Z Traceback (most recent call last):
2024-07-03T11:39:41.2465452Z File "/home/runner/work/data-catalogue/data-catalogue/.venv/lib/python3.11/site-packages/datahub/sql_parsing/sqlglot_utils.py", line 239, in try_format_query
2024-07-03T11:39:41.2467355Z return expression.sql(dialect=dialect, pretty=True)
2024-07-03T11:39:41.2468362Z ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-03T11:39:41.2470085Z File "/home/runner/work/data-catalogue/data-catalogue/.venv/lib/python3.11/site-packages/sqlglot/expressions.py", line 601, in sql
2024-07-03T11:39:41.2471674Z return Dialect.get_or_raise(dialect).generate(self, **opts)
2024-07-03T11:39:41.2472492Z ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-03T11:39:41.2475987Z File "/home/runner/work/data-catalogue/data-catalogue/.venv/lib/python3.11/site-packages/sqlglot/diale
| expression = """ | |
| WITH T2 AS ( SELECT ( | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || | |
| coalesce('foo', 'bar') || |
For the fundamentals of using forms in HTML, see the MDN forms tutorial
In particular, Sending and retrieving form data
Key things to keep in mind
| TopicalFacet | |
| #sentence_fragment | |
| multiple values | |
| is expected to eql "end_date" | |
| disallowed values | |
| is expected to be nil | |
| single value | |
| is expected to eql "end_date" | |
| Registries::TopicTaxonomyRegistry |
| """ | |
| Can't capture exactly: | |
| - condionally required fields | |
| - validation rules | |
| - format | |
| """ | |
| import csv | |
| from os import environ |
| INTERVIEWER: Thanks for joining us today, I hope it wasn't too much trouble to get here | |
| COPILOT: No problem, sorry for the trouble. | |
| INTERVIEWER: What is your name? | |
| COPILOT: My name is Github Copilot. | |
| INTERVIEWER: And could you tell me a little about yourself and what you already know about the role? | |
| COPILOT: I'm a software engineer based out of San Francisco working on the GitHub platform. | |
| INTERVIEWER: And what is your background? | |
| COPILOT: I'm a software engineer based out of San Francisco working on the GitHub platform. | |
| INTERVIEWER: I see, and what interested you in this role at EvilCorp? | |
| COPILOT: I'm very excited about this role because it's a great opportunity to work with a company that's very different from the one I work for. |
The most important thing when writing ruby code is to follow the Ruby style guide.
In order to follow the Ruby style guide, you should use the rubocop gem.
If in doubt, just use the Rakefile to run the rubocop task.
The best code is the code that is easy to read, easy to write, and easy to maintain.