Skip to content

Conversation

@duvvuvenkataramana
Copy link

This change addresses issue #4898 and related duplicate reports where users encounter different behavior between Linux and Windows when using push_back with braced json objects.

The issue is caused by brace initialization behavior, which is documented as a known limitation in the FAQ at https://json.nlohmann.me/home/faq/#brace-initialization-yields-arrays

By adding a prominent reminder to check the FAQ before reporting, we hope to reduce the frequency of duplicate issue reports for this known behavior.

[Describe your pull request here. Please read the text below the line and make sure you follow the checklist.]

  • The changes are described in detail, both the what and why.
  • If applicable, an existing issue is referenced.
  • The Code coverage remained at 100%. A test case for every new line of code.
  • If applicable, the documentation is updated.
  • The source code is amalgamated by running make amalgamate.

Read the Contribution Guidelines for detailed information.

This change addresses issue nlohmann#4898 and related duplicate reports where users encounter different behavior between Linux and Windows when using push_back with braced json objects.

The issue is caused by brace initialization behavior, which is documented as a known limitation in the FAQ at https://json.nlohmann.me/home/faq/#brace-initialization-yields-arrays

By adding a prominent reminder to check the FAQ before reporting, we hope to reduce the frequency of duplicate issue reports for this known behavior.

Signed-off-by: duvvuvenkataramana <[email protected]>
@coveralls
Copy link

coveralls commented Nov 24, 2025

Coverage Status

coverage: 99.191%. remained the same
when pulling 9c71b97 on duvvuvenkataramana:patch-1
into a0e9fb1 on nlohmann:develop.

@github-actions github-actions bot added M and removed S labels Nov 24, 2025
@duvvuvenkataramana
Copy link
Author

@gregmarr @nlohmann
Thanks for reviewing the PR!

I've updated the bug report template so that the FAQ reminder is now placed in the correct location—right after the note that the form is for bug reports only, as suggested. This should make the guidance clearer for users and help reduce duplicate issue reports.

Please let me know if any further changes are needed. Happy to adjust anything!

@gregmarr
Copy link
Contributor

@duvvuvenkataramana That looks better. I'll let @nlohmann comment on the overall changes.

@duvvuvenkataramana
Copy link
Author

@nlohmann @gregmarr — thanks for reviewing the PR!

@duvvuvenkataramana
Copy link
Author

@nlohmann Now I added valuable links . Check

Signed-off-by: duvvuvenkataramana <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants