You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the user chooses HCL2 (vs JSON) as the format to display the template code samples on a page, the choice does not stick and switches back to the JSON format (which seems to be the default) when the same page is displayed again (e.g. after desktop focus is lost and regained). I tested with both FF and Chrome on Windows 10.
Please fix documentation pages to remember code sample choice made by the user. Better yet, make HCL2 the default for such code samples, as HCL2 is the preferred template format while JSON is the legacy format. By default, code samples should display in the HCL2 format, with the JSON version only displayed if the user clicks on it.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
A paragraph or two about the issue you're experiencing.
Reproduction Steps
Steps to reproduce this issue
Packer version
From packer version
Simplified Packer Template
If the file is longer than a few dozen lines, please include the URL to the gist of the log or use the Github detailed
format
instead of posting it directly in the issue.
Operating system and Environment details
OS, Architecture, and any other information you can provide about the
environment.
Log Fragments and crash.log files
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Set the env var PACKER_LOG=1 for maximum log detail.
The text was updated successfully, but these errors were encountered:
sabuncumurat
changed the title
Please fix documentation pages to remember template choice selected by user for examples
Please fix documentation pages to remember template format choice selected by user for examples
Jun 27, 2024
sabuncumurat
changed the title
Please fix documentation pages to remember template format choice selected by user for examples
Please fix documentation pages to remember code sample choice selected by user for examples and use HCL2 as the default format
Jun 27, 2024
sabuncumurat
changed the title
Please fix documentation pages to remember code sample choice selected by user for examples and use HCL2 as the default format
Please fix documentation pages to remember code sample choice selected by user and use HCL2 as the default format
Jun 27, 2024
Agreed on the labelling there @tenthirtyam, thanks!
You are correct @sabuncumurat, HCL2 should be the new normal these days, we should do a pass on the docs to change that behaviour.
We'll see to it ASAP, thanks for the report
Example page exhibiting the problem: https://developer.hashicorp.com/packer/docs/provisioners/breakpoint
When the user chooses HCL2 (vs JSON) as the format to display the template code samples on a page, the choice does not stick and switches back to the JSON format (which seems to be the default) when the same page is displayed again (e.g. after desktop focus is lost and regained). I tested with both FF and Chrome on Windows 10.
Please fix documentation pages to remember code sample choice made by the user. Better yet, make HCL2 the default for such code samples, as HCL2 is the preferred template format while JSON is the legacy format. By default, code samples should display in the HCL2 format, with the JSON version only displayed if the user clicks on it.
Community Note
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
A paragraph or two about the issue you're experiencing.
Reproduction Steps
Steps to reproduce this issue
Packer version
From
packer version
Simplified Packer Template
If the file is longer than a few dozen lines, please include the URL to the
gist of the log or use the Github detailed
format
instead of posting it directly in the issue.
Operating system and Environment details
OS, Architecture, and any other information you can provide about the
environment.
Log Fragments and crash.log files
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Set the env var
PACKER_LOG=1
for maximum log detail.The text was updated successfully, but these errors were encountered: