fix: adding branch in url for search entities#36938
Conversation
|
Warning
|
| File Path | Change Summary |
|---|---|
app/client/src/pages/common/SearchBar/... |
Modified navigateToApplication to handle Git-enabled applications and updated viewURL logic. |
Assessment against linked issues
| Objective | Addressed | Explanation |
|---|---|---|
| Ensure that the default branch is used when launching applications via search (36782) | ✅ |
Possibly related PRs
- fix: loading state for pull #36363: This PR modifies the state management related to Git operations, which is relevant to the changes made in the
navigateToApplicationfunction in the main PR that also involves Git metadata. - fix: fixing cta for git import modal #36364: This PR updates the Git import modal's call-to-action, which relates to the overall Git functionality being enhanced in the main PR's changes to the
EntitySearchBarcomponent. - fix: Airgap: search bar UI was not matching with release #36772: This PR addresses UI consistency in the search bar, which is directly related to the
EntitySearchBarcomponent being modified in the main PR.
Suggested labels
Medium, UX Improvement, Query & JS Pod
Suggested reviewers
- ankitakinger
- hetunandu
📜 Recent review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- app/client/src/pages/common/SearchBar/EntitySearchBar.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- app/client/src/pages/common/SearchBar/EntitySearchBar.tsx
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?
🪧 Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.Generate unit testing code for this file.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:@coderabbitai generate unit testing code for this file.@coderabbitai modularize this function.
- PR comments: Tag
@coderabbitaiin a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.@coderabbitai read src/utils.ts and generate unit testing code.@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.@coderabbitai help me debug CodeRabbit configuration file.
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)
@coderabbitai pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
Documentation and Community
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.
| const defaultBranch = | ||
| searchedApplication?.gitApplicationMetadata?.defaultBranchName; | ||
|
|
||
| viewURL = viewerURL({ |
There was a problem hiding this comment.
@brayn003 Out of curiosity, shouldn't the routeBuilder have taken care of this routing? This way, we would have been sure that all instances of this route builder are routing accurately and are taking the Git default branch into account. Can you help me understand why that is either not possible, or complicated?
## Description Fixes application redirection issue from search bar ~ 1. Appends branch to the url Fixes appsmithorg#36782 ## Automation /ok-to-test tags="@tag.Git" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/11390479742> > Commit: 02eb26e > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=11390479742&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Git` > Spec: > <hr>Thu, 17 Oct 2024 18:34:15 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No
Description
Fixes application redirection issue from search bar ~
Fixes #36782
Automation
/ok-to-test tags="@tag.Git"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11390479742
Commit: 02eb26e
Cypress dashboard.
Tags:
@tag.GitSpec:
Thu, 17 Oct 2024 18:34:15 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?