Fix issue: unprintable character is rendered when handling comments in j2 #16287
Conversation
…n j2
Use "{#-" and "-#}" to mark comments in jinja template
Signed-off-by: Stephen Sun <[email protected]>
|
@stephenxs to which branches this is needed? master only? |
@liat-grozovik The issue was introduced when the license was added as the file header in PR #16096 which has been back-ported to 202211 only so far. So I added a tag for 202211 only (cleanly cherry-picked based on the latest 202211 commit e7ce179) |
…n j2 (sonic-net#16287) Use "{#-" and "-#}" to mark comments in jinja template Signed-off-by: Stephen Sun <[email protected]>
|
Cherry-pick PR to 202211: #16421 |
|
@stephenxs PR conflicts with 202305 branch |
Thanks @mssonicbld |
…n j2 (#16287) Use "{#-" and "-#}" to mark comments in jinja template Signed-off-by: Stephen Sun <[email protected]>
mssonicbld
added
Included in 202211 Branch
and removed
Approved for 202211 Branch
Created PR to 202211 Branch
labels
…n j2 (sonic-net#16287) Use "{#-" and "-#}" to mark comments in jinja template Signed-off-by: Stephen Sun <[email protected]>
Use "{#-" and "-#}" to mark comments in jinja template
Why I did it
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)