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.

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

Prepopulate additional non-stated settings with its default value #32

Open
egberts opened this issue May 30, 2022 · 2 comments
Open

Prepopulate additional non-stated settings with its default value #32

egberts opened this issue May 30, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@egberts
Copy link
Owner

egberts commented May 30, 2022

Might be more useful if the unstated settings (of named.conf) has its default values and seeded in the final PyParsing object tree.

@egberts egberts self-assigned this May 30, 2022
@egberts egberts changed the title Prepopulate additional non-stated settings with its default calue Prepopulate additional non-stated settings with its default valur May 30, 2022
@egberts egberts changed the title Prepopulate additional non-stated settings with its default valur Prepopulate additional non-stated settings with its default value May 30, 2022
@egberts
Copy link
Owner Author

egberts commented May 30, 2022

Probably best done outside of PyParsing effort.

Perhaps as an added .seed_with_defaults Python method added to the bind9_parser Class or something.

@egberts
Copy link
Owner Author

egberts commented Jun 2, 2022

Definitely have to be given a version number before default values can be determined, which is to be expected anyway

@egberts egberts added the enhancement New feature or request label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant