#266 A Footer for the webpage #291
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!291
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#266-make-a-footer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A footer has now been made which scales with the size of the main content and is always at the bottom of the page.
I have reviewed the footer implementation on the current branch.
The footer renders correctly and is visible and no errors were observed as the application builds and runs successfully.
Code review findings:
Improvements:
Issues:
Conclusion:
the implementation technically works correctly and meets the requirements so there are no blocking issues found but it requires fixing to be regarded complete.
I can see that this PR has already been reviewed, but I have also gone through the implementation myself.
The footer is rended correctly and the component structure with CSS modules looks good.
As @b24krila mentioned about the screen, I guess it may be caused by the use of fixed spacing ( margin-left) together with (repeat(4, 1fr)) part in footer.js which may cause issues on smaller screens ( I guess).
The code standard is fulfilled for the most part , apart from smal syntax inconsistencies, such as missing semicolons.
Overall the implementation works and are good!
Merged manually
Pull request closed