Skip to content
This repository was archived by the owner on Mar 12, 2024. It is now read-only.

Bugfix: Navigating to the settings page#347

Closed
baristaGeek wants to merge 1 commit intodevfrom
bugfix/settings-page-doenst-have-proper-behavior
Closed

Bugfix: Navigating to the settings page#347
baristaGeek wants to merge 1 commit intodevfrom
bugfix/settings-page-doenst-have-proper-behavior

Conversation

@baristaGeek
Copy link
Collaborator

Description

Settings page has a werid behavior

Type of change

  • 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)
  • Documentation update
  • Chore: cleanup/renaming, etc
  • RFC

Notes

The NextJS docs say this: https://nextjs.org/docs/messages/react-hydration-error

Acceptance

@vercel
Copy link

vercel bot commented Oct 27, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
watermelon ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 27, 2023 10:51pm

@watermelon-copilot-for-code-review

WatermelonAI Summary

The first commit in this PR is related to the export loading in the settings loading page. The PR title suggests that there was a bug while navigating to the settings page. The PR body provides some context about the weird behavior experienced with the settings page. From this information, it seems that the bug is related to the loading functionality on the settings page, and this commit attempts to fix that bug.

GitHub PRs

Click here to login to Jira
Click here to login to Confluence
Click here to login to Slack
Notion Pages deactivated by baristaGeek
Linear Tickets deactivated by baristaGeek
Click here to login to Asana
watermelon is an open repo and Watermelon will serve it for free.
🍉🫶

@EstebanDalelR
Copy link
Member

Fixed in #348

@baristaGeek
Copy link
Collaborator Author

Closing because this was fixed in #348

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants