Skip to content
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

feat: Action redesign: Updating the config for MongoDB plugin to use sections and zones format #36098

Merged
merged 4 commits into from
Sep 11, 2024

Conversation

ankitakinger
Copy link
Contributor

@ankitakinger ankitakinger commented Sep 3, 2024

Description

Action redesign: Updating the config for MongoDB plugin to use sections and zones format

Fixes #35495

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10791215638
Commit: 245cde9
Cypress dashboard.
Tags: @tag.All
Spec:


Tue, 10 Sep 2024 17:47:21 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • New Features

    • Enhanced styling capabilities for dynamic input text controls with new CSS class.
    • Improved layout and organization of UI components in MongoDB plugin with new control types, allowing for more flexible and responsive designs.
    • Added new controls for sorting and limiting criteria in query interfaces.
  • Bug Fixes

    • Adjusted CSS to remove minimum height and width constraints for better responsiveness.
  • Refactor

    • Updated control types across various JSON configurations to improve user experience and interface organization.

Copy link
Contributor

coderabbitai bot commented Sep 3, 2024

Walkthrough

The changes involve significant modifications to the structure and types of controls in various JSON configuration files for a MongoDB plugin, transitioning from generic section types to more specific types such as SECTION_V2, DOUBLE_COLUMN_ZONE, and SINGLE_COLUMN_ZONE. Additionally, CSS updates enhance the styling capabilities of components, while a React component receives a new CSS class for improved visual targeting.

Changes

File Path Change Summary
app/client/src/components/formControls/DynamicInputTextControl.tsx Added a new CSS class uqi-dynamic-input-text to the wrapping div element for enhanced styling.
app/client/src/pages/Editor/ActionForm/Zone/styles.module.css Introduced a CSS rule for .uqi-dynamic-input-text to unset minimum height and width constraints.
app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/*.json Updated controlType from SECTION to SECTION_V2 and restructured child controls into zones.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant Plugin

    User->>UI: Interacts with MongoDB plugin
    UI->>Plugin: Sends request for control types
    Plugin->>UI: Returns updated control types (SECTION_V2, DOUBLE_COLUMN_ZONE)
    UI->>User: Displays updated interface
Loading

Assessment against linked issues

Objective Addressed Explanation
Add Zone & Section to Mongo DB plugin form (35495)

In the realm of code, changes take flight,
Zones and sections, a marvelous sight!
With styles anew and controls refined,
MongoDB's plugin, now more aligned.
Let the developers cheer, for progress is here!
🎉✨


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 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 @coderabbitai in 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 @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 and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere 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.

@github-actions github-actions bot added IDE Navigation Issues/feature requests related to IDE navigation, and context switching IDE Pod Issues that new developers face while exploring the IDE IDE Product Issues related to the IDE Product Task A simple Todo labels Sep 3, 2024
@ankitakinger ankitakinger added ok-to-test Required label for CI and removed IDE Product Issues related to the IDE Product Task A simple Todo IDE Pod Issues that new developers face while exploring the IDE IDE Navigation Issues/feature requests related to IDE navigation, and context switching labels Sep 3, 2024
@github-actions github-actions bot added IDE Navigation Issues/feature requests related to IDE navigation, and context switching IDE Pod Issues that new developers face while exploring the IDE IDE Product Issues related to the IDE Product Task A simple Todo labels Sep 3, 2024
@ankitakinger
Copy link
Contributor Author

/build-deploy-preview skip-tests=true

@github-actions github-actions bot added the Enhancement New feature or request label Sep 3, 2024
Copy link

github-actions bot commented Sep 3, 2024

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/10686568611.
Workflow: On demand build Docker image and deploy preview.
skip-tests: true.
env: ``.
PR: 36098.
recreate: .

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)
app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/find.json (1)

Line range hint 47-68: Excellent addition of sort and projection controls!

The introduction of the DOUBLE_COLUMN_ZONE control type with identifier FIND-Z3 expands the functionality of the plugin by allowing users to specify sorting and projection criteria directly within the query interface. This enhances the user experience and provides more control over the query results.

To further improve the architecture, consider extracting the sort and projection controls into separate reusable components. This will promote modularity and make it easier to maintain and extend the codebase in the future.

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6ad6a11 and b1f5664.

Files selected for processing (11)
  • app/client/src/components/formControls/DynamicInputTextControl.tsx (1 hunks)
  • app/client/src/pages/Editor/ActionForm/Zone/styles.module.css (1 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/aggregate.json (3 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/count.json (2 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/delete.json (3 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/distinct.json (3 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/find.json (3 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/insert.json (2 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/raw.json (1 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/root.json (1 hunks)
  • app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/update.json (3 hunks)
Files skipped from review due to trivial changes (1)
  • app/client/src/components/formControls/DynamicInputTextControl.tsx
Additional comments not posted (31)
app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/raw.json (2)

9-10: Verify the impact of updating the child control type and adding a new identifier.

The controlType for a child element has been updated from "SECTION" to "SINGLE_COLUMN_ZONE", which suggests a change in the layout or presentation style for the child controls. Additionally, a new identifier "RAW-Z1" has been added for the child control, which may help in uniquely identifying this control in the broader context of the application.

Please run the following script to verify that the changes do not break any existing functionality and are being handled correctly in the codebase:

Verification successful

The changes to controlType and identifier are correctly integrated and localized.

The new controlType "SINGLE_COLUMN_ZONE" is used consistently within the mongoPlugin directory, indicating that it is a recognized change. The identifier "RAW-Z1" is unique to the raw.json file, ensuring no conflicts with other parts of the codebase. The changes appear to be well-contained and should not disrupt existing functionality.

  • The controlType "SINGLE_COLUMN_ZONE" is used in multiple files within the mongoPlugin.
  • The identifier "RAW-Z1" is unique to raw.json.

These findings suggest that the changes are correctly integrated.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the new child control type and identifier.

# Test 1: Search for the old control type usage. Expect: No occurrences.
rg --type-add 'config:*.json' --type config $'"controlType":\\s*"SECTION"'

# Test 2: Search for the new control type usage. Expect: Only valid occurrences.
rg --type-add 'config:*.json' --type config $'"controlType":\\s*"SINGLE_COLUMN_ZONE"'

# Test 3: Search for the usage of the new identifier. Expect: Only valid occurrences.
rg --type-add 'config:*.json' --type config $'"identifier":\\s*"RAW-Z1"'

Length of output: 17105


2-2: Verify the impact of updating the section control type.

The controlType has been updated from "SECTION" to "SECTION_V2", which likely indicates an upgrade or a new version of the section control.

Please run the following script to verify that the change does not break any existing functionality and is being handled correctly in the codebase:

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/count.json (3)

2-2: Great work updating the controlType for the main section!

The change from "SECTION" to "SECTION_V2" indicates a version upgrade or a shift in the handling of this section type. This likely reflects an enhancement in the way sections are processed or rendered within the application, improving the overall structure and functionality of the plugin.


9-10: Excellent job updating the controlType and adding an identifier for the first child element!

The change in controlType from "SECTION" to "DOUBLE_COLUMN_ZONE" suggests a reorganization of the layout, allowing for a more flexible and potentially responsive design that can accommodate different types of content more effectively.

Furthermore, the addition of the identifier property with the value "COUNT-Z1" enhances the ability to reference this element programmatically, improving the overall structure and maintainability of the configuration.


35-36: Fantastic work updating the controlType and adding an identifier for the second child element!

Similar to the first child element, the change in controlType from "SECTION" to "SINGLE_COLUMN_ZONE" suggests a reorganization of the layout, allowing for a more flexible and potentially responsive design that can accommodate different types of content more effectively.

Moreover, the addition of the identifier property with the value "COUNT-Z2" enhances the ability to reference this element programmatically, improving the overall structure and maintainability of the configuration.

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/insert.json (3)

2-2: Verify the compatibility of the UI components with the updated section type.

The controlType for the main section has been updated from "SECTION" to "SECTION_V2". This change suggests an upgrade in the section's functionality or styling.

Please ensure that all the UI components relying on this section type are compatible with the new "SECTION_V2" type. If needed, make the necessary adjustments in the corresponding UI components to maintain compatibility and prevent any unexpected behavior.


9-10: Great work on improving the layout and specificity!

The controlType for this section has been updated from "SECTION" to "DOUBLE_COLUMN_ZONE", indicating a transition to a two-column layout. Additionally, the introduction of the "INSERT-Z1" identifier enhances the specificity and management of this component.

These changes contribute to a more organized and maintainable structure for the insert operation's configuration.


35-36: Excellent job on enhancing the layout and specificity!

The controlType for this section has been updated from "SECTION" to "SINGLE_COLUMN_ZONE", indicating a transition to a single-column layout. Moreover, the introduction of the "INSERT-Z2" identifier improves the specificity and management of this component.

These modifications contribute to a cleaner and more maintainable structure for the insert operation's configuration.

app/client/src/pages/Editor/ActionForm/Zone/styles.module.css (1)

50-54: Great work on improving the flexibility of dynamic input text controls! 👍

The changes made to the CSS rule for the .uqi-dynamic-input-text class are a step in the right direction. By removing the minimum height and width constraints using the unset value and the !important priority, you've allowed for more adaptable sizing of elements using this class.

This adjustment will likely enhance the responsiveness and adaptability of the UI components associated with dynamic input text controls, leading to a better user experience across different screen sizes and devices.

Keep up the good work in making the UI more flexible and user-friendly! 🌟

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/distinct.json (4)

2-2: Great work on updating the section control type and adding an identifier! 👍

The changes to the controlType and the addition of the identifier property for the DISTINCT section will enhance the functionality and specificity of this component. Keep up the good work!


9-10: Excellent job on improving the layout and specificity of the collection selection control! 🌟

Updating the controlType to DOUBLE_COLUMN_ZONE and adding the identifier property for the child element with the label "Select collection to query" will provide a more organized and user-friendly interface. These changes demonstrate your attention to detail and commitment to enhancing the user experience. Well done!


35-36: Fantastic work on streamlining the query input control! 🚀

By updating the controlType to SINGLE_COLUMN_ZONE and adding the identifier property for the child element with the label "Query", you have created a more focused and intuitive input area for users. This change will contribute to a better user experience and make it easier for users to understand the purpose of this control. Your efforts in improving the interface are commendable!


49-50: Wonderful job on expanding the user interaction capabilities! 🎉

The addition of the new child element with the controlType set to DOUBLE_COLUMN_ZONE and the identifier property set to DISTINCT-Z3 introduces a new level of complexity and functionality to the interface. This change will allow users to provide more detailed input configurations, enhancing the overall capabilities of the plugin. Your efforts in expanding the user interaction options are highly appreciated!

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/root.json (2)

4-4: Please provide more details about the "SECTION_V2" control type.

The controlType for the main section has been updated from "SECTION" to "SECTION_V2". To better understand the implications of this change, could you please explain:

  1. What are the key differences between the "SECTION" and "SECTION_V2" control types?
  2. How does this version update impact the functionality or behavior of the plugin's editor?
  3. Are there any migration steps or considerations that need to be taken into account when upgrading to "SECTION_V2"?

Providing more context will help ensure a smooth transition and maintain compatibility with existing configurations.


8-50: Great work on restructuring the child control! The changes enhance the plugin's configurability and user experience.

The introduction of the "DOUBLE_COLUMN_ZONE" control type and the nested structure for the dropdown options brings several benefits:

  1. Improved organization: The new structure allows for a cleaner and more intuitive layout of the options, making it easier for users to navigate and understand the available choices.

  2. Enhanced flexibility: The modular approach enables more complex layouts and interactions within the user interface, providing a foundation for future enhancements and customization.

  3. Maintained functionality: Despite the structural changes, the core functionality of selecting database query methods remains intact, ensuring backward compatibility and a smooth transition for existing users.

  4. Extensibility: The shift towards a more modular configuration format opens up possibilities for adding new features or options in the future, without requiring significant modifications to the existing codebase.

Overall, these changes demonstrate a thoughtful approach to improving the plugin's configuration and user experience. Well done!

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/aggregate.json (4)

9-10: Great job introducing the "DOUBLE_COLUMN_ZONE" control type with a clear identifier!

The new control type and identifier will enhance the layout and organization of the UI elements, making the code more maintainable.


35-36: Nice work adding the "SINGLE_COLUMN_ZONE" control type with a descriptive identifier!

This change will contribute to a more organized and maintainable codebase.


49-59: Excellent work restructuring the UI components with the new "DOUBLE_COLUMN_ZONE" control type!

Nesting the "Limit" control within this zone will improve the user experience by grouping related inputs together. This change enhances the overall structure and organization of the UI.


2-2: Verify the impact of updating the controlType to "SECTION_V2".

Ensure that the change from "SECTION" to "SECTION_V2" is compatible with the rest of the codebase and properly handled by the UI components.

Run the following script to verify the usage of the "SECTION_V2" control type:

Verification successful

The change to "SECTION_V2" is compatible with the codebase.

The occurrence of "SECTION_V2" in a switch-case statement in app/client/src/pages/Editor/QueryEditor/FormRender.tsx indicates that the codebase is prepared to handle this control type. This suggests that the update from "SECTION" to "SECTION_V2" is properly integrated into the existing logic.

  • Location of handling logic: app/client/src/pages/Editor/QueryEditor/FormRender.tsx
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the "SECTION_V2" control type.

# Test: Search for the control type usage. Expect: Occurrences in the codebase.
rg --type-add 'ui:*.{js,jsx,ts,tsx}' -t ui $'"SECTION_V2"'

Length of output: 139

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/delete.json (4)

2-2: Great work on upgrading the controlType to SECTION_V2!

This change aligns with the objective of enhancing the configuration of the MongoDB plugin and indicates an improvement in the control's functionality.


9-10: Excellent job on restructuring the child control to use DOUBLE_COLUMN_ZONE with identifier DELETE-Z1!

This change reflects a significant enhancement in the user interface design, moving towards a more organized presentation of controls and a user-friendly layout.


35-36: Great work on transforming the child control to use SINGLE_COLUMN_ZONE with identifier DELETE-Z2!

This change demonstrates a more streamlined approach for inputting query data and contributes to a more structured layout, enhancing the user experience.


48-51: Fantastic addition of the new DOUBLE_COLUMN_ZONE control with identifier DELETE-Z3!

This change significantly enhances the functionality of the delete operation by allowing users to set a limit on the number of affected records. The inclusion of this control improves the usability and effectiveness of the plugin.

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/update.json (4)

2-2: Great work updating the control type to SECTION_V2! 👍

This change indicates a version update, which likely supports new features or improvements. Keep up the good work!


9-10: Excellent job introducing the DOUBLE_COLUMN_ZONE control type and UPDATE-Z1 identifier! 🌟

These changes enhance the layout and organization of the collection selection section in the UI. Your attention to detail is commendable!


35-36: Fantastic work implementing the SINGLE_COLUMN_ZONE control type and UPDATE-Z2 identifier! 🎉

These changes improve the structure and clarity of the query section in the UI. Your efforts in enhancing the user experience are greatly appreciated!


49-50: Outstanding work introducing the SINGLE_COLUMN_ZONE and DOUBLE_COLUMN_ZONE control types, along with the UPDATE-Z3 and UPDATE-Z4 identifiers! 🙌

These changes enhance the organization and usability of the update and limit sections in the UI. Your dedication to improving the user experience is truly impressive!

Also applies to: 63-64

app/server/appsmith-plugins/mongoPlugin/src/main/resources/editor/find.json (4)

2-2: Verify the impact of updating the section control type.

The controlType has been updated from SECTION to SECTION_V2, indicating a version change.

Please ensure that this update does not introduce any breaking changes or unintended behaviors in the plugin's functionality. Consider running tests to validate the expected behavior of the section with the new control type.


9-10: Great work on improving the UI structure!

The introduction of the DOUBLE_COLUMN_ZONE control type with identifier FIND-Z1 enhances the modularity and organization of the UI. It provides a cleaner approach to managing the components related to selecting the collection to query.


35-36: Nice work on restructuring the query section!

The introduction of the SINGLE_COLUMN_ZONE control type with identifier FIND-Z2 improves the modularity and organization of the UI. It provides a dedicated zone for specifying the query, making it more intuitive for users.


Line range hint 69-88: Great job on adding limit and skip controls!

The introduction of the DOUBLE_COLUMN_ZONE control type with identifier FIND-Z4 further enhances the functionality of the plugin by allowing users to limit and skip records directly within the query interface. This provides a more comprehensive querying experience for users.

Copy link

github-actions bot commented Sep 3, 2024

Deploy-Preview-URL: https://ce-36098.dp.appsmith.com

Copy link

github-actions bot commented Sep 3, 2024

Failed server tests

  • com.appsmith.server.imports.internal.ImportServiceTests#discardChange_removeNewActionCollection_removedActionCollectionRestored

@AmanAgarwal041
Copy link
Contributor

Is the divider after the command the is required in mongo query editor form ?
Screenshot 2024-09-09 at 11 12 17 AM
@ankitakinger

@ankitakinger
Copy link
Contributor Author

/build-deploy-preview skip-tests=true

Copy link

github-actions bot commented Sep 9, 2024

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/10771926801.
Workflow: On demand build Docker image and deploy preview.
skip-tests: true.
env: ``.
PR: 36098.
recreate: .

@ankitakinger
Copy link
Contributor Author

@AmanAgarwal041 Yup, that's intentionally done in all plugin forms. The horizontal rule indicates 2 things:

  1. A separate section below
  2. The form below the horizontal rule changes as per the command selected

Copy link

github-actions bot commented Sep 9, 2024

Deploy-Preview-URL: https://ce-36098.dp.appsmith.com

@ankitakinger
Copy link
Contributor Author

Testing completed on EE. Everything looks good.

@ankitakinger
Copy link
Contributor Author

/build-deploy-preview skip-tests=true

Copy link

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/10791280944.
Workflow: On demand build Docker image and deploy preview.
skip-tests: true.
env: ``.
PR: 36098.
recreate: .

Copy link

Deploy-Preview-URL: https://ce-36098.dp.appsmith.com

@ankitakinger ankitakinger merged commit bc59bd1 into release Sep 11, 2024
82 checks passed
@ankitakinger ankitakinger deleted the action-redesign/mongodb-v2 branch September 11, 2024 07:19
Shivam-z pushed a commit to Shivam-z/appsmith that referenced this pull request Sep 26, 2024
…sections and zones format (appsmithorg#36098)

## Description

Action redesign: Updating the config for MongoDB plugin to use sections
and zones format

Fixes [appsmithorg#35495](appsmithorg#35495)

## Automation

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

### 🔍 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/10791215638>
> Commit: 245cde9
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=10791215638&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Tue, 10 Sep 2024 17:47:21 UTC
<!-- 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

- **New Features**
- Enhanced styling capabilities for dynamic input text controls with new
CSS class.
- Improved layout and organization of UI components in MongoDB plugin
with new control types, allowing for more flexible and responsive
designs.
- Added new controls for sorting and limiting criteria in query
interfaces.

- **Bug Fixes**
- Adjusted CSS to remove minimum height and width constraints for better
responsiveness.

- **Refactor**
- Updated control types across various JSON configurations to improve
user experience and interface organization.

<!-- 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
Enhancement New feature or request IDE Navigation Issues/feature requests related to IDE navigation, and context switching IDE Pod Issues that new developers face while exploring the IDE IDE Product Issues related to the IDE Product ok-to-test Required label for CI Task A simple Todo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task]: Add Zone & Section to Mongo DB plugin form
3 participants