fix: Removed on page load edges from layout model

[nidhi-nair]

Description

Since an Appsmith application is not limited by the number of interconnections it can make, it is possible for users to create graphs so complex that we end up having MBs of data in a relatively simple page as well. This was causing failures in a user's app since they were now unable to update their app any further. We do not really use this property anywhere in our logic today, and this is essentially redundant information. This PR gets rid of the edges property from the layout and runs a migrations to clean up all existing pages as well.

If we do find a need for this property in the future, a simple update layout on each of these pages would do the trick.

Fixes #20680

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Manual

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

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:

• Test plan has been approved by relevant developers
• Test plan has been peer reviewed by QA
• Cypress test cases have been added and approved by either SDET or manual QA
• Organized project review call with relevant stakeholders after Round 1/2 of QA
• Added Test Plan Approved label after reveiwing all Cypress test

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
appsmith	⬜️ Ignored (Inspect)			Mar 1, 2023 at 0:14AM (UTC)

[nidhi-nair]

/ok-to-test sha=7c4f6a8

[github-actions]

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4292567885.
Workflow: Appsmith External Integration Test Workflow.
Commit: 7c4f6a8.
PR: 21038.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21038&runId=4292567885_1

[sondermanish]

LGTM

[github-actions]

The following are new failures, please fix them before merging the PR

1. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/Form/Form_With_CheckBox_spec.js

[github-actions]

The following are new failures, please fix them before merging the PR

1. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/Form/Form_With_CheckBox_spec.js

[nidhi-nair]

/ok-to-test sha=1d0eeb6

[github-actions]

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4303404007.
Workflow: Appsmith External Integration Test Workflow.
Commit: 1d0eeb6.
PR: 21038.
Perf tests will be available at https://app.appsmith.com/app/performance-infra-dashboard/pr-details-638dd7cd2913ba43778b915e?pr=21038&runId=4303404007_1

[github-actions]

The following are new failures, please fix them before merging the PR

1. cypress/integration/Regression_TestSuite/ClientSideTests/Autocomplete/Autocomplete_JS_spec.ts
2. cypress/integration/Regression_TestSuite/ClientSideTests/Binding/Bind_tableApi_spec.js
3. cypress/integration/Regression_TestSuite/ClientSideTests/Binding/InputWidgets_NavigateTo_validation_spec.js
4. cypress/integration/Regression_TestSuite/ClientSideTests/Binding/SelectWidget_Spec.ts
5. cypress/integration/Regression_TestSuite/ClientSideTests/Binding/TableV2_ClientSide_Search_spec.js
6. cypress/integration/Regression_TestSuite/ClientSideTests/Binding/TableV2_Widget__CondtionalFormatting_spec.js
7. cypress/integration/Regression_TestSuite/ClientSideTests/Branding/Branding_spec.js
8. cypress/integration/Regression_TestSuite/ClientSideTests/BugTests/AbortAction_Spec.ts
9. cypress/integration/Regression_TestSuite/ClientSideTests/BugTests/CatchBlock_Spec.ts
10. cypress/integration/Regression_TestSuite/ClientSideTests/BugTests/MultipleOnPageLoadConfirmation_Spec.ts
11. cypress/integration/Regression_TestSuite/ClientSideTests/FormNativeToRawTests/Mongo_spec.ts
12. cypress/integration/Regression_TestSuite/ClientSideTests/GenerateCRUD/Generate_Crud_New_Page_spec.ts
13. cypress/integration/Regression_TestSuite/ClientSideTests/OtherUIFeatures/ForkApplication_spec.js
14. cypress/integration/Regression_TestSuite/ClientSideTests/SettingsPane/PageSettings_spec.ts
15. cypress/integration/Regression_TestSuite/ClientSideTests/VisualTests/JSEditorComment_spec.js
16. cypress/integration/Regression_TestSuite/ClientSideTests/VisualTests/WidgetsLayout_spec.js
17. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/Datepicker/DatePicker_With_Switch_spec.js
18. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/JSONForm/JSONForm_AutoGenerateFormDisabled_spec.js
19. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/List/List5_spec.js
20. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/ListV2/Listv2_BasicServerSideData_spec.js
21. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/Modal_background_spec.ts
22. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/Radio/RadioGroup2_spec.js
23. cypress/integration/Regression_TestSuite/ClientSideTests/Widgets/TableV1/Table_Number_column_spec.js
24. cypress/integration/Regression_TestSuite/ServerSideTests/Datasources/MockDBs_spec.ts
25. cypress/integration/Regression_TestSuite/ServerSideTests/OnLoadTests/JSOnLoad2_Spec.ts
26. cypress/integration/Regression_TestSuite/UpgradeAppsmith/UpgradeAppsimth_spec.js

[coderabbitai]

Warning

Rate limit exceeded

@Nikhil-Nandagopal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 8 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between f90d3fc and 1d0eeb6.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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