Skip to content

chore: Only send uidString to remove a JSLib#34473

Merged
sharat87 merged 2 commits intoreleasefrom
sharat87-patch-3
Jun 26, 2024
Merged

chore: Only send uidString to remove a JSLib#34473
sharat87 merged 2 commits intoreleasefrom
sharat87-patch-3

Conversation

@sharat87
Copy link
Member

@sharat87 sharat87 commented Jun 25, 2024

Part of #33724. The server uses only uidString for this API endpoint, which is all we should be sending. The server accepts a few other fields as well today, but doesn't use them. That'll also be fixed in the future, to only accept strictly what's needed.

/test sanity js

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9672660446
Commit: a61fa21
Cypress dashboard.
Tags: @tag.Sanity, @tag.JS

Summary by CodeRabbit

  • Bug Fixes

    • Improved the updateLibrary method to send specific payload data, enhancing API reliability.
  • Logging Improvements

    • Updated log messages in the removeJSLibFromApplication method to exclude version information for better clarity.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 25, 2024

Walkthrough

The updates consist of a more specific payload being sent in the updateLibrary method of the LibraryAPI.tsx file, and an update to the log message in the CustomJSLibControllerCE.java file to remove version information from the JS library being removed.

Changes

Files Change Summary
app/client/src/api/LibraryAPI.tsx Updated updateLibrary method to send a specific payload { accessor: library.accessor, url: library.url } instead of the entire library object.
app/server/appsmith-server/src/main/java/.../CustomJSLibControllerCE.java Removed version information from log message in removeJSLibFromApplication method.

Poem

As lines of code align anew,
Payloads find a path more true,
Logs now speak a simpler rhyme,
Version free, in perfect time.
With each tweak, our system grows,
Crafting swift and clever flows.
— A rabbit’s joy, as coding shows. 🐰💻


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 as 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.

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.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

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 the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Jun 25, 2024
@sharat87 sharat87 added the ok-to-test Required label for CI label Jun 25, 2024
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: 1

Outside diff range and nitpick comments (1)
app/client/src/api/LibraryAPI.tsx (1)

Line range hint 5-33: Consider refactoring to use simple functions instead of a class with only static methods.

Classes with only static methods often signal that a module with simple functions might be more appropriate. This would also address the lint warning and align the design with functional programming practices, which are generally favored in JavaScript for such use cases.

- export default class LibraryApi extends Api {
-   static base_url = "v1/libraries";
-   static getUpdateLibraryBaseURL = (applicationId: string) => `${LibraryApi.base_url}/${applicationId}`;
-   static async addLibrary(applicationId: string, library: Partial<JSLibrary> & { defs: string }) {
-     const url = LibraryApi.getUpdateLibraryBaseURL(applicationId) + "/add";
-     return Api.patch(url, library);
-   }
-   static async removeLibrary(applicationId: string, library: Partial<JSLibrary>) {
-     const url = LibraryApi.getUpdateLibraryBaseURL(applicationId) + "/remove";
-     return Api.patch(url, { uidString: library.uidString });
-   }
-   static async getLibraries(applicationId: string, mode: APP_MODE) {
-     const url = `${LibraryApi.getUpdateLibraryBaseURL(applicationId)}${mode === APP_MODE.PUBLISHED ? "/view" : ""}`;
-     return Api.get(url);
-   }
- }
+ export const base_url = "v1/libraries";
+ export const getUpdateLibraryBaseURL = (applicationId: string) => `${base_url}/${applicationId}`;
+ export async function addLibrary(applicationId: string, library: Partial<JSLibrary> & { defs: string }) {
+   const url = getUpdateLibraryBaseURL(applicationId) + "/add";
+   return Api.patch(url, library);
+ }
+ export async function removeLibrary(applicationId: string, library: Partial<JSLibrary>) {
+   const url = getUpdateLibraryBaseURL(applicationId) + "/remove";
+   return Api.patch(url, { uidString: library.uidString });
+ }
+ export async function getLibraries(applicationId: string, mode: APP_MODE) {
+   const url = `${getUpdateLibraryBaseURL(applicationId)}${mode === APP_MODE.PUBLISHED ? "/view" : ""}`;
+   return Api.get(url);
+ }

Consider this refactor to improve modularity and align with best practices in JavaScript.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 519b53e and 6b5b480.

Files selected for processing (1)
  • app/client/src/api/LibraryAPI.tsx (1 hunks)
Additional context used
Biome
app/client/src/api/LibraryAPI.tsx

[error] 5-33: Avoid classes that contain only static members. (lint/complexity/noStaticOnlyClass)

Prefer using simple functions instead of classes with only static members.

@sharat87 sharat87 added ok-to-test Required label for CI and removed ok-to-test Required label for CI labels Jun 26, 2024
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 and nitpick comments (1)
app/client/src/api/LibraryAPI.tsx (1)

Line range hint 5-33: Consider refactoring to use utility functions instead of a static-only class.

The static analysis tool has flagged the use of a class that only contains static methods. This can be refactored into a series of utility functions, which may simplify the structure and enhance maintainability.

- export default class LibraryApi extends Api {
-   static base_url = "v1/libraries";
-   ...
- }
+ const base_url = "v1/libraries";
+ export const getUpdateLibraryBaseURL = (applicationId: string) => `${base_url}/${applicationId}`;
+ ...
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6b5b480 and a61fa21.

Files selected for processing (2)
  • app/client/src/api/LibraryAPI.tsx (1 hunks)
  • app/server/appsmith-server/src/main/java/com/appsmith/server/controllers/ce/CustomJSLibControllerCE.java (1 hunks)
Additional context used
Learnings (2)
Common learnings
User: nidhi-nair
PR: appsmithorg/appsmith#29372
File: app/server/appsmith-server/src/main/java/com/appsmith/server/applications/jslibs/ApplicationJsLibServiceCEImpl.java:51-56
Timestamp: 2023-12-06T08:42:30.719Z
Learning: The `updateJsLibsInContext` method in the `ApplicationJsLibServiceCEImpl` class was mistakenly referred to as a new method in a previous comment. It is important to accurately assess the context of changes in a pull request to avoid misrepresenting the nature of the code modifications.
app/server/appsmith-server/src/main/java/com/appsmith/server/controllers/ce/CustomJSLibControllerCE.java (1)
User: nidhi-nair
PR: appsmithorg/appsmith#29372
File: app/server/appsmith-server/src/main/java/com/appsmith/server/applications/jslibs/ApplicationJsLibServiceCEImpl.java:51-56
Timestamp: 2023-12-06T08:42:30.719Z
Learning: The `updateJsLibsInContext` method in the `ApplicationJsLibServiceCEImpl` class was mistakenly referred to as a new method in a previous comment. It is important to accurately assess the context of changes in a pull request to avoid misrepresenting the nature of the code modifications.
Biome
app/client/src/api/LibraryAPI.tsx

[error] 5-33: Avoid classes that contain only static members. (lint/complexity/noStaticOnlyClass)

Prefer using simple functions instead of classes with only static members.

Additional comments not posted (2)
app/client/src/api/LibraryAPI.tsx (1)

24-24: Refine payload to increase specificity and security.

The change to send only { accessor: library.accessor, url: library.url } is aligned with the PR's objective to ensure that only necessary data is sent. This minimizes potential security risks and reduces bandwidth usage.

app/server/appsmith-server/src/main/java/com/appsmith/server/controllers/ce/CustomJSLibControllerCE.java (1)

64-65: Simplified log statement enhances clarity and reduces potential PII exposure.

Updating the log statement to exclude version information and focus on uidString aligns with the goal of minimizing unnecessary data exposure. This change is a good practice in terms of security and data privacy.

@sharat87 sharat87 added ok-to-test Required label for CI and removed ok-to-test Required label for CI labels Jun 26, 2024
@sharat87 sharat87 requested review from mohanarpit and riodeuno June 26, 2024 04:11
@sharat87 sharat87 merged commit 854d3f0 into release Jun 26, 2024
@sharat87 sharat87 deleted the sharat87-patch-3 branch June 26, 2024 05:28
sharat87 added a commit that referenced this pull request Jun 27, 2024
Currently, if the incoming request body contains fields that aren't
recognized by the backend, we just ignore them, and deserialize what we
_can_. This has lead to subtle bugs and wasted a lot of developer time
in the past, and added little value in return.

Most recently, with application creation, now fixed in
#33722.

Another one, for action creation, client sends this in `eventData` field
of the request body:

![shot-2024-05-26-04-50-46](https://github.com/appsmithorg/appsmith/assets/120119/b876b27f-47ec-4a00-8598-33cb92120c49)
But the class defined for `eventData` is this:

![shot-2024-05-26-04-51-03](https://github.com/appsmithorg/appsmith/assets/120119/18bf46b7-597a-4b2f-8355-1b8fad30e4ce)
Clearly isn't working.

This PR enabled the `FAIL_ON_UNKNOWN_PROPERTIES` setting only for the
deserialization of HTTP request payloads. It shouldn't have impact on
other deserializations like those for Git, and those that load resource
files. Primarily to limit the scope.

This should also bring in some much-needed type strictness to the client
as well. So far, server has been lax in accepting just any fields in the
incoming request body, so client was able to afford being lax about the
object that was sent up.

We're enabling this restriction only for CE currently. Will be opening a
similar PR on EE and once all tests pass there, we enable for EE as
well.

Depends on #33728 #33730 #33731 #34366 #34405 #34446 #34473 #34506


Run No. 1
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9685619413>
> Commit: 04e225f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9685619413&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: ``

**/test all**
























<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9690185000>
> Commit: 29da8b4
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9690185000&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: ``

<!-- end of auto-generated comment: Cypress test results  -->



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

## Summary by CodeRabbit

- **New Features**
- Added `certificateType` property to datasources for enhanced SSL
configuration options.

- **Enhancements**
- Improved JSON deserialization behavior for better data handling and
flexibility.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Shivam-z pushed a commit to Shivam-z/appsmith that referenced this pull request Jul 10, 2024
Part of appsmithorg#33724. The server uses only `uidString` for this API endpoint,
which is all we should be sending. The server accepts a few other fields
as well today, but doesn't use them. That'll also be fixed in the
future, to only accept strictly what's needed.

/test sanity js



<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9672660446>
> Commit: a61fa21
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9672660446&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity, @tag.JS`

<!-- end of auto-generated comment: Cypress test results  -->






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

- **Bug Fixes**
- Improved the `updateLibrary` method to send specific payload data,
enhancing API reliability.

- **Logging Improvements**
- Updated log messages in the `removeJSLibFromApplication` method to
exclude version information for better clarity.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Shivam-z pushed a commit to Shivam-z/appsmith that referenced this pull request Jul 10, 2024
Currently, if the incoming request body contains fields that aren't
recognized by the backend, we just ignore them, and deserialize what we
_can_. This has lead to subtle bugs and wasted a lot of developer time
in the past, and added little value in return.

Most recently, with application creation, now fixed in
appsmithorg#33722.

Another one, for action creation, client sends this in `eventData` field
of the request body:

![shot-2024-05-26-04-50-46](https://github.com/appsmithorg/appsmith/assets/120119/b876b27f-47ec-4a00-8598-33cb92120c49)
But the class defined for `eventData` is this:

![shot-2024-05-26-04-51-03](https://github.com/appsmithorg/appsmith/assets/120119/18bf46b7-597a-4b2f-8355-1b8fad30e4ce)
Clearly isn't working.

This PR enabled the `FAIL_ON_UNKNOWN_PROPERTIES` setting only for the
deserialization of HTTP request payloads. It shouldn't have impact on
other deserializations like those for Git, and those that load resource
files. Primarily to limit the scope.

This should also bring in some much-needed type strictness to the client
as well. So far, server has been lax in accepting just any fields in the
incoming request body, so client was able to afford being lax about the
object that was sent up.

We're enabling this restriction only for CE currently. Will be opening a
similar PR on EE and once all tests pass there, we enable for EE as
well.

Depends on appsmithorg#33728 appsmithorg#33730 appsmithorg#33731 appsmithorg#34366 appsmithorg#34405 appsmithorg#34446 appsmithorg#34473 appsmithorg#34506


Run No. 1
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9685619413>
> Commit: 04e225f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9685619413&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: ``

**/test all**
























<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9690185000>
> Commit: 29da8b4
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9690185000&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: ``

<!-- end of auto-generated comment: Cypress test results  -->



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

## Summary by CodeRabbit

- **New Features**
- Added `certificateType` property to datasources for enhanced SSL
configuration options.

- **Enhancements**
- Improved JSON deserialization behavior for better data handling and
flexibility.

<!-- 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

ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants