Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should we deny unknown fields in configuration files? #1569

Open
yangby-cryptape opened this issue Nov 17, 2023 · 0 comments
Open

Should we deny unknown fields in configuration files? #1569

yangby-cryptape opened this issue Nov 17, 2023 · 0 comments
Labels
d:confirmation Discussion required to confirm whether it's a bug

Comments

@yangby-cryptape
Copy link
Collaborator

PROS

  • To avoid users think some fields works but not.

    • To avoid typos.

    • Users know deprecated fields immediately after upgrade the Axon binary.

  • Reserve the names of fields.
@yangby-cryptape yangby-cryptape changed the title [Discuss] Should we deny unknown fields in configuration files? Should we deny unknown fields in configuration files? Nov 24, 2023
@yangby-cryptape yangby-cryptape added the d:confirmation Discussion required to confirm whether it's a bug label Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
d:confirmation Discussion required to confirm whether it's a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yangby-cryptape