Make json and yaml available in templates

[RachitSharma2001]

closes: #27079

It was suggested that a macro be added that allows for the deserialization of json or yaml strings (since yaml is a superset of jsons, I just deserialized using yaml).

I also added tests for this macro in tests/macro.

I would also be open to adding this functionality to the system tests if that is needed.

[Taragolis]

Some nits

Also we should add info into the Templates reference documentation. Otherwise how users would know how to use this macro?

[Taragolis]

deserialize it is a bit broad name which could mean everything and might confuse users.

[RachitSharma2001]

Sounds good! I have integrated the requested changes in my latest push, including changing the name of the macro from deseralize to json_loads.

However, in terms of the documentation, I think it will already automatically be added to the templates reference. This is because this macro is a macro function, specified in airflow/macros along with ds_add, ds_format, datetime_diff_for_humans). In the bottom of templates_ref.rst, it loads the documentation provided for each function in the that macro file. So I think the documentation I added to the json_loads macro (specified in the comment provided under the function) will actually be linked in the templates reference. Let me know if this is correct or if my understanding is wrong.

[uranusjr]

I’d prefer adding two separate macros, one for only JSON and another for YAML support.

[RachitSharma2001]

Sounds good! I have created those two separate macros and have rebased. Let me know if any other changes are needed.

[uranusjr]

Hmm, looking at other things in the module, I wonder if we should simply import json and yaml into it, so users can just write {{ json.loads(...) }} instead of needing to remember a slightly different syntax.

[potiuk]

Hmm, looking at other things in the module, I wonder if we should simply import json and yaml into it, so users can just write {{ json.loads(...) }} instead of needing to remember a slightly different syntax.

Yeah. It woudl be useful to add json/yaml generic imports for many other use cases. The only potential problem is safety of those, but I think those two shoudl be rather safe to add.

[RachitSharma2001]

That makes sense. Would it still make sense to keep the tests on json and yaml, or should those be removed too?

Fixed

[potiuk]

Keeping two tests is fine.

[uranusjr]

As a follow up, those noqa comments should be removed and replaced by an explicit whitelist.

[RachitSharma2001]

Hi everyone, it seems like this PR is approved. I was wondering if there is anything else that should be updated or changed? If so, let me know.

[RachitSharma2001]

Hi everyone, it seems like this PR has been approved and passes all the tests. I was wondering if there is anything else that should be updated or changed? If so, let me know.

[RachitSharma2001]

Hi everyone, I was wondering, since the changes on this branch have been approved and it seems to be passing all the tests, if the branch could be merged into main? Or if there is anything else that needs to be updated or changed, let me know.