At present, footer can be customised with only text and background colour. Many clients came up asking for more customisations. So, we decided to add a render prop to footer which will accept component.
Dependencies # (dependency-issue-reference)
Update framework version to get this change in frontend.
Documentation # (link to the corresponding documentation changes)
Yes. Documentation needs to updated with new render prop
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
Pass a custom component or div to the render prop in frontend app. And check whether it is reflecting it the frontend in place of footer.
If not passed, default footer should render.
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
Description
At present, footer can be customised with only text and background colour. Many clients came up asking for more customisations. So, we decided to add a render prop to footer which will accept component.
Dependencies # (dependency-issue-reference) Update framework version to get this change in frontend.
Documentation # (link to the corresponding documentation changes) Yes. Documentation needs to updated with new render prop
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist: