Skip to content

fix: Resolving datasource page redirection, switch env and on page load response view debugger issues#30156

Merged
ankitakinger merged 2 commits intoreleasefrom
fix/modules-bugs
Jan 10, 2024
Merged

fix: Resolving datasource page redirection, switch env and on page load response view debugger issues#30156
ankitakinger merged 2 commits intoreleasefrom
fix/modules-bugs

Conversation

@ankitakinger
Copy link
Copy Markdown
Contributor

@ankitakinger ankitakinger commented Jan 9, 2024

Description

Resolving datasource page redirection, switch env and on page load response view debugger issues.

PR fixes following issue(s)

Fixes #30158

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

  • Manual
  • JUnit
  • Jest
  • Cypress

Checklist:

Dev activity

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • PR is being merged under a feature flag

QA activity:

  • Speedbreak features have been covered
  • Test plan covers all impacted features and areas of interest
  • Test plan has been peer reviewed by project stakeholders and other QA members
  • Manually tested functionality on DP
  • We had an implementation alignment call with stakeholders post QA Round 2
  • Cypress test cases have been added and approved by SDET/manual QA
  • Added Test Plan Approved label after Cypress tests were reviewed
  • Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

  • New Features
    • Introduced a message prompt for the environment switching process.
    • Enabled automatic generation of editor paths for datasources when not found.
  • Enhancements
    • Improved user experience by streamlining the process of storing as a datasource in the editor.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 9, 2024

Walkthrough

The recent updates involve enhancing the user interface components related to environment switching and datasource management. A new callback function for messaging has been introduced to the switch environment component. Additionally, there is a focus on improving the handling of editor paths for datasources, ensuring that editor paths are generated when needed, which is reflected in both the user interface and the sagas managing the application state.

Changes

File Path Change Summary
.../SwitchEnvironment/index.tsx Added a new function type property startSwitchEnvMessage to the Props interface.
.../BottomBar/index.tsx Imported START_SWITCH_ENVIRONMENT message and passed startSwitchEnvMessage prop to SwitchEnvironment component.
.../StoreAsDatasource.tsx
.../DatasourceStructureNotFound.tsx
.../DatasourcesSagas.ts
Included a new property generateEditorPath set to true in various objects, suggesting an enhancement in the logic for generating editor paths for datasources.

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?

Share

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>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in 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 generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@ankitakinger ankitakinger changed the title fixing datasource page redirection, switch env and on page load respo… fix: Resolving datasource page redirection, switch env and on page load response view debugger issues Jan 9, 2024
@github-actions github-actions bot added Bug Something isn't working Task A simple Todo labels Jan 9, 2024
@ankitakinger
Copy link
Copy Markdown
Contributor Author

/ok-to-test tags="@tag.All"

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Whoa, @tag.All spotted in your test suite! 🚀
While @tag.All is cool, like a catch-all net, why not try specific tags? 🏷️
Narrow down your suite with specific tags for quicker and more accurate tests! 🚀 Less waiting, more zipping through tests like a ninja!
Explore the tags documentation here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7458800216.
Workflow: Appsmith External Integration Test Workflow.
Tags: ``.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7458800216.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@ankitakinger
Copy link
Copy Markdown
Contributor Author

/ok-to-test tags="@tag.All"

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Whoa, @tag.All spotted in your test suite! 🚀
While @tag.All is cool, like a catch-all net, why not try specific tags? 🏷️
Narrow down your suite with specific tags for quicker and more accurate tests! 🚀 Less waiting, more zipping through tests like a ninja!
Explore the tags documentation here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7459605066.
Workflow: Appsmith External Integration Test Workflow.
Tags: ``.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7458800216.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7459605066.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/QueryPane/DSDocs_Spec.ts
  4. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7459605066.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js

  2. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7459605066.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js

To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7459605066.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js

To know the list of identified flaky tests - Refer here

@github-actions github-actions bot added Frontend This label marks the issue or pull request to reference client code Packages Pod issues that belong to the packages pod labels Jan 9, 2024
@ankitakinger
Copy link
Copy Markdown
Contributor Author

/ok-to-test tags="@tag.All"

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Whoa, @tag.All spotted in your test suite! 🚀
While @tag.All is cool, like a catch-all net, why not try specific tags? 🏷️
Narrow down your suite with specific tags for quicker and more accurate tests! 🚀 Less waiting, more zipping through tests like a ninja!
Explore the tags documentation here

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Workflow: Appsmith External Integration Test Workflow.
Tags: ``.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 9, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/ApiTests/API_Bugs_Spec.js
  4. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/ApiTests/API_Bugs_Spec.js
  4. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

  2. cypress/e2e/Regression/ClientSide/OtherUIFeatures/Omnibar_spec.js
  3. cypress/e2e/Regression/ServerSide/QueryPane/GoogleSheets_spec.ts
To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/BugTests/DSDiscardBugs_spec.ts

To know the list of identified flaky tests - Refer here

@github-actions
Copy link
Copy Markdown

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7466657889.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

@ankitakinger ankitakinger merged commit dca4682 into release Jan 10, 2024
@ankitakinger ankitakinger deleted the fix/modules-bugs branch January 10, 2024 13:11
dipyamanbiswas07 pushed a commit that referenced this pull request Jan 11, 2024
…ad response view debugger issues (#30156)

## Description

Resolving datasource page redirection, switch env and on page load
response view debugger issues.

#### PR fixes following issue(s)
Fixes [#30158](#30158)

#### Type of change
- Bug fix (non-breaking change which fixes an issue)
- Chore (housekeeping or task changes that don't impact user perception)

## Testing

#### How Has This Been Tested?
- [x] Manual
- [ ] JUnit
- [x] Jest
- [x] Cypress

## Checklist:
#### Dev activity
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag


#### QA activity:
- [ ] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [ ] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [ ] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
	- Introduced a message prompt for the environment switching process.
- Enabled automatic generation of editor paths for datasources when not
found.
- **Enhancements**
- Improved user experience by streamlining the process of storing as a
datasource in the editor.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Frontend This label marks the issue or pull request to reference client code Packages Pod issues that belong to the packages pod Task A simple Todo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Listed bugs for modules

2 participants