-
Notifications
You must be signed in to change notification settings - Fork 2
add more validators for attributes and menus and tweak configuration … #66
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Combodo always uses
1or an empty value fordo_search, I did as well.Should we allow empty values or do we want to restrict this even against use case of Combodo itself?
They only check if it contains
1or not: https://github.com/Combodo/iTop/blob/8580cb70a41c0b7be36a6b40a993bc3bcf5276fa/setup/compiler.class.inc.php#L2856There 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.
The configuration that combodo does is sometimes very strange. It does not look like it is following some design guides. Sometimes they use true or false, or not present, sometimes they use 1 or anything else, sometimes it is completely different again. I also found occurences of elements that allow a bunch of entries that do all the same - even with some kind of typos in it.
I also thought about this specific element. My idea was to "raise awareness" if there is someting like "true" or "false" (because it would be obvious). but as true would be wrong, I would like to have this as an error in the validation.
At the moment I do not see any other usecase as having the element to be 1 or simply not present, not even empty.
And as having 0 or empty or not present or anything else (not 1) does nothing, it will not hurt.
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.
Thanks for the reply, will need to update my data models then 😉