Allow user to define HoneypotDataProperty for functional Volt #124
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.
Related to #122
Problem
We're unable to use the package in Volt using functional syntax
Cause
The package depends on Reflection to guess the HoneypotData property, by checking which property has the HoneypotData type. Unfortunately, this is incompatible with Volt using functional syntax.
Solution
Add a method in the
UsesSpamProtection
traitgetHoneypotDataProperty
that allows user to specify which property is the HoneypotData property. If not specified, it falls back to Reflection to guess the property