#789-Socials-Page #792
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!792
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#789-Socials-Page"
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?
Added a social page that the footer social button links to. Only the page has been added with no fucntional links to School socials, that will be a seperate issue
Originial issue is #789 #789
Scrolling to the top on click is being fixed in a separate issue by b23albst
Review on #792
What has been Done.
Reviewed the code and tested if the socials page exists and is reachable
Tested on Windows Using Microsoft Edge and Google Chrome
App starts
Footer is visible and can be interacted with
The placeholder takes you to the socials page.
Found the issue that is being worked on by b23albst
Inspected the following files "App.js" , "Footer.js", "Socials.js", "index.js"
What needs to be done
Question
In this pull-request there seems to be included files that do not correlate to the current issue:
My question is are these supposed to be here or is there a mistake because otherwise I see no problems.
Conclusion
In conclusion the issue seems to have been solved the pull-request is a bit weird but after an answer the issue can be merged without and problems.
Deploy changes was never intentionally made but seemed to have happened for some reason and weather graph is one to one with already existing weather graph in the team branch.
My guess is that the deploy change and showing of weather graph as beign brand new is just github and vscode hallucinations caused by me only doing a fetch on main and not on the team branch in specific before creating this branch. I reverted the deploy change as that actually removed code. But the Weather graph is 1 to 1 so it should be fine as long as there are no merge conflicts. But try to make note of this branch if any future troubles happen with the temperature graph or deployment just in case.