-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: duplicate page name error does not disappear on navigating to other pages #36320
fix: duplicate page name error does not disappear on navigating to other pages #36320
Conversation
WalkthroughThe changes introduced in this pull request involve the addition of a Changes
Assessment against linked issues
Suggested labels
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
…-error-does-not-disappear
app/client/src/pages/Editor/AppSettingsPane/AppSettings/PageSettings.tsx
Outdated
Show resolved
Hide resolved
…-error-does-not-disappear
… of https://github.com/a6hishekpandey/appsmith into fix/35949-duplicate-page-name-error-does-not-disappear
/build-deploy-preview skip-tests=true |
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/10901989464. |
Deploy-Preview-URL: https://ce-36320.dp.appsmith.com |
…-error-does-not-disappear
@a6hishekpandey everything seems to be in order, we just need to run the test suite on a shadow PR, however some tests are failing for reasons unrelated to your changes, so we need to wait until the issue is resolved. Just keeping you updated. |
@alex-golovanov okay, thanks for the update. |
@alex-golovanov can you please check now if PR is ready for approval or not? |
The situation with failing tests has not been resolved yet, I'm keeping an eye on it, we'll merge this once everything is in order. |
All tests are passing in the shadow PR. |
…her pages (appsmithorg#36320) ## Description **Issue:** Duplicate page name error does not disappear on navigating to other pages. This PR addresses issue appsmithorg#35949 by resetting the isPageNameValid state to undefined using useEffect hook when the Page settings loads. Fixes appsmithorg#35949 > [!WARNING] > _If no issue exists, please create an issue first, and check with the maintainers if the issue is valid._ ## Automation /ok-to-test tags="" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!CAUTION] > If you modify the content in this section, you are likely to disrupt the CI result for your PR. <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Bug Fixes** - Improved page name validation by resetting its state when the page data updates, ensuring accurate checks based on new information. - **Style** - Minor formatting adjustment for better code readability. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Description
Issue: Duplicate page name error does not disappear on navigating to other pages.
This PR addresses issue #35949 by resetting the isPageNameValid state to undefined using useEffect hook when the Page settings loads.
Fixes #35949
Warning
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.
Automation
/ok-to-test tags=""
🔍 Cypress test results
Caution
If you modify the content in this section, you are likely to disrupt the CI result for your PR.
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit