Existing code was unconditionally setting RateLimitSecurityBindings.CONFIG to null in the component constructor.
Which is problematic for cases when this config is bound by user before adding the component.
This PR removes the need of setting config binding after the component is constructed by adding a condition that checks if the config options are already present.
GH-116
Fixes #116
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
[ ] Test A
[ ] Test B
Checklist:
[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules
Description
Existing code was unconditionally setting
RateLimitSecurityBindings.CONFIGto null in the component constructor. Which is problematic for cases when this config is bound by user before adding the component.This PR removes the need of setting config binding after the component is constructed by adding a condition that checks if the config options are already present.
GH-116
Fixes #116
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: