feat: Add support for JSON/XML/model rules source when loading rules … #21
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.
…from module settings
The current syntax for module cbsecurity rules only appears to support a
rules[]
array when pullingcbSecurity
module settings from the module'ssettings
struct. (See module rules documentation for example.)This commit adds support for full JSON/XML/model rules so folks can use their rule syntax of choice in module configurations.
For example, the following now works to pull in rules from
#modulePath#/config/security.json.cfm
:Previously, this would throw an error:
The RULES argument passed to the normalizeRules function is not of type array
, precisely because only anarray
of rules was supported or expected in cbSecurity configuration pulled from a module.