-
Notifications
You must be signed in to change notification settings - Fork 34
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
Limit old profile_example.json to only properties not used in default profile and rename it #1120
Limit old profile_example.json to only properties not used in default profile and rename it #1120
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works for me. But I will wait for other reviews before approving.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me!
I think I like having a single file that lists all available properties. It feels odd to me to have a second file with only extra parameters. But I understand that having 2 files is harder to maintain. |
@PNAX, I agree that there are pros and cons, but my conclusion is to resolve #1118 with this PR. Do you have another proposal how to resolve the issue? |
I don't have any better idea for now. Maybe just a suggestion on renaming |
I have no problem with that, and I think you have a valid point. I will update this PR with an updated file name. |
078814d
to
5904b19
Compare
@PNAX, please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
beside the typo, this looks good to me
docs/Profiles.md
Outdated
[Profile properties]: https://metacpan.org/pod/Zonemaster::Engine::Profile#PROFILE-PROPERTIES | ||
The content of the two files, as-is or modified, can be merged into a custom | ||
profile file that can be loaded by Zonemaster-Engine. Both Zonemaster-CLI and | ||
Zonemaster-Backend has direct options for loading a custom profile file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: "has" -> "have"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected.
@mattias-p, are you also fine with the new name? Please re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Updates to reflect the name change of share/profile_example.json to share/profile_additional_properties.json. * Adds further clarifications on custom profile file.
74e1136
to
9cb721c
Compare
Conflict resolved by rebasing. |
@tgreenx and @mattias-p, can you re-approve? The PR has been rebased to resolve a conflict. |
Purpose
Today
profile_example.json
is a superset of profile.json, or almost. Every timeprofile.json
is updatedprofile_example.json
should also be updated, but that does not always happen. To resolve that problem this PR makesprofile_example.json
limited to the properties that are not present in the default profile, and it is renamed to better reflect the new content.Profiles.md
is also updated.The only file in Zonemaster-Engine that reference to
profile_example.json
isProfiles.md
. No other repository has any reference to the file.Context
#1118
How to test this PR
Documentation only.