Skip to content

test: Remove unused data in DSL fixtures#34405

Merged
sharat87 merged 2 commits intoreleasefrom
chore/dsl-jsons
Jun 24, 2024
Merged

test: Remove unused data in DSL fixtures#34405
sharat87 merged 2 commits intoreleasefrom
chore/dsl-jsons

Conversation

@sharat87
Copy link
Member

@sharat87 sharat87 commented Jun 23, 2024

Part of #33724.

We have a lot of fixture files in our Cypress tests with DSLs of various kinds. They are used to update the DSL using the /api/v1/layouts/{layoutId}/pages/{pageId}?applicationId={applicationId}.

This API, is in this line in LayoutControllerCE, and the request body is parsed as objects of LayoutUpdateDTO record. This record, accepts only the dsl field, and nothing else.

List of potential files that have this problem was identified with this command:

cd app/client/cypress
rg -Io 'AddDsl\(".+?\)' \
  | cut -d\" -f2 \
  | sort -u \
  | while read line; do
    if rg -q '"(layoutOnLoadActions|layoutOnLoadActionErrors|userPermissions|new)":' fixtures/"$line".json; then
      echo $line
    fi
  done

(For reference, and to use on EE repo, after this is merged).

/test all

Caution

🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9633990737
Commit: 9e848f1
Cypress dashboard.
Tags: ``
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor3_spec.ts
  2. cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor_1_spec.js
  3. cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor_2_spec.js
List of identified flaky tests.

Summary by CodeRabbit

  • Bug Fixes

    • Corrected the file path for loading DSL configuration in the nested list widget scenario.
  • Chores

    • Streamlined multiple JSON files by removing deprecated layoutOnLoadActions arrays and other obsolete fields, resulting in cleaner and more manageable configurations.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 23, 2024

Walkthrough

The changes focus on simplifying JSON configurations used in the Cypress test scenarios. Primarily, the layoutOnLoadActions, alongside other fields like layoutOnLoadActionErrors, id, and userPermissions have been removed from various fixture files. Additionally, a path correction has been made in a test script to improve the loading of a DSL file, thus possibly impacting the behavior of a nested list widget.

Changes

Files Change Summary
.../Event_Bindings_spec.ts Modified the path in agHelper.AddDsl from "Listv2/nestedList.json" to "Listv2/nestedList".
Multiple JSON files (.json files: CMSdsl.json, ChartTextDsl.json, Js_toggle_dsl.json, ..., layoutdsl.json) Removed layoutOnLoadActions arrays.
Multiple JSON files (anvilButtonWidget.json, anvilIconButtonWidget.json, ..., publishedModeToastToggleDsl.json) Removed layoutOnLoadActions, layoutOnLoadActionErrors, id, and userPermissions fields.
slashcommandDsl.json Removed layoutOnLoadActions and new fields.

Poem

A breeze of change through JSON fields,
Simplified, our testing yields.
Fixtures now with less to load,
A sprightly hop along the code.
Widgets bloom in newfound light,
Our tests run smooth, both day and night. 🐇✨


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.

@sharat87 sharat87 changed the title Remove unused data in DSL fixtures chore: Remove unused data in DSL fixtures Jun 23, 2024
@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 23, 2024
@sharat87 sharat87 changed the title chore: Remove unused data in DSL fixtures test: Remove unused data in DSL fixtures Jun 23, 2024
@github-actions github-actions bot added the Test label Jun 23, 2024
@sharat87 sharat87 added the ok-to-test Required label for CI label Jun 23, 2024
@sharat87 sharat87 marked this pull request as ready for review June 23, 2024 16:47
@sharat87 sharat87 requested a review from ApekshaBhosale as a code owner June 23, 2024 16:47
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 71bc84f and 9e848f1.

Files selected for processing (20)
  • app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Event_Bindings_spec.ts (1 hunks)
  • app/client/cypress/fixtures/CMSdsl.json (1 hunks)
  • app/client/cypress/fixtures/ChartTextDsl.json (1 hunks)
  • app/client/cypress/fixtures/Js_toggle_dsl.json (1 hunks)
  • app/client/cypress/fixtures/Mapdsl.json (1 hunks)
  • app/client/cypress/fixtures/PageLoadDsl.json (1 hunks)
  • app/client/cypress/fixtures/PgAdmindsl.json (1 hunks)
  • app/client/cypress/fixtures/SimpleBinding.json (1 hunks)
  • app/client/cypress/fixtures/TextTableV2dsl.json (1 hunks)
  • app/client/cypress/fixtures/TextTabledsl.json (1 hunks)
  • app/client/cypress/fixtures/anvilButtonWidget.json (1 hunks)
  • app/client/cypress/fixtures/anvilIconButtonWidget.json (1 hunks)
  • app/client/cypress/fixtures/anvilInlineButtonWidget.json (1 hunks)
  • app/client/cypress/fixtures/anvilToolbarButtonWidget.json (1 hunks)
  • app/client/cypress/fixtures/commondsl.json (1 hunks)
  • app/client/cypress/fixtures/displayWidgetDsl.json (1 hunks)
  • app/client/cypress/fixtures/formdsl.json (1 hunks)
  • app/client/cypress/fixtures/layoutdsl.json (1 hunks)
  • app/client/cypress/fixtures/publishedModeToastToggleDsl.json (2 hunks)
  • app/client/cypress/fixtures/slashcommandDsl.json (1 hunks)
Files skipped from review due to trivial changes (19)
  • app/client/cypress/fixtures/CMSdsl.json
  • app/client/cypress/fixtures/ChartTextDsl.json
  • app/client/cypress/fixtures/Js_toggle_dsl.json
  • app/client/cypress/fixtures/Mapdsl.json
  • app/client/cypress/fixtures/PageLoadDsl.json
  • app/client/cypress/fixtures/PgAdmindsl.json
  • app/client/cypress/fixtures/SimpleBinding.json
  • app/client/cypress/fixtures/TextTableV2dsl.json
  • app/client/cypress/fixtures/TextTabledsl.json
  • app/client/cypress/fixtures/anvilButtonWidget.json
  • app/client/cypress/fixtures/anvilIconButtonWidget.json
  • app/client/cypress/fixtures/anvilInlineButtonWidget.json
  • app/client/cypress/fixtures/anvilToolbarButtonWidget.json
  • app/client/cypress/fixtures/commondsl.json
  • app/client/cypress/fixtures/displayWidgetDsl.json
  • app/client/cypress/fixtures/formdsl.json
  • app/client/cypress/fixtures/layoutdsl.json
  • app/client/cypress/fixtures/publishedModeToastToggleDsl.json
  • app/client/cypress/fixtures/slashcommandDsl.json
Additional comments not posted (1)
app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Event_Bindings_spec.ts (1)

16-16: Address reported test failures in Rich Text Editor widget tests.

The PR description mentions new test failures in several Rich Text Editor widget tests. It's crucial to investigate these failures to ensure they are not caused by the changes made to the DSL files. Review the changes in the affected DSL files and verify if they align with the expected behavior in these tests.

@riodeuno
Copy link
Contributor

@sharat87 Perhaps the RTE test suites are using the removed keys from the fixtures? It seems unlikely, but the tests for the RTE have failed. Let me know if you need help looking into these.

@sharat87
Copy link
Member Author

Thanks @riodeuno. Those tests are failing in release branch already. See Slack thread.

I'm going to go ahead and merge this PR in soon, since those tests are already failing in the base branch.

@sharat87 sharat87 merged commit dc79ebb into release Jun 24, 2024
@sharat87 sharat87 deleted the chore/dsl-jsons branch June 24, 2024 11:47
sharat87 added a commit that referenced this pull request Jun 26, 2024
Part of #33724, and extension to #34405.

This file's contents are used to call the endpoint:

```
/layouts/{layoutId}/pages/{pageId}?applicationId={applicationId}
```

But this endpoint accepts request payload as `LayoutUpdateDTO`, which
only has one single field, `dsl`, and nothing else.

But the way we use this JSON, is that we're sending the body as this:

```json
{
  "widgetName": "MainContainer",
  "backgroundColor": "none",
  "rightColumn": 1296,
  "snapColumns": 64,
  "detachFromLayout": true,
  "widgetId": "0",
  "topRow": 0,
  "bottomRow": 440,
  "containerStyle": "none",
  "snapRows": 125,
  "parentRowSpace": 1,
  "type": "CANVAS_WIDGET",
  "canExtend": true,
  "version": 47,
  "minHeight": 420,
  "parentColumnSpace": 1,
  "dynamicBindingPathList": [],
  "leftColumn": 0,
  "children": []
}
```

Not as this:
```json
{
  "dsl": {
    "widgetName": "MainContainer",
    "backgroundColor": "none",
    "rightColumn": 1296,
    "snapColumns": 64,
    "detachFromLayout": true,
    "widgetId": "0",
    "topRow": 0,
    "bottomRow": 440,
    "containerStyle": "none",
    "snapRows": 125,
    "parentRowSpace": 1,
    "type": "CANVAS_WIDGET",
    "canExtend": true,
    "version": 47,
    "minHeight": 420,
    "parentColumnSpace": 1,
    "dynamicBindingPathList": [],
    "leftColumn": 0,
    "children": []
  }
}
```

Which means that we aren't sending anything useful.


/test widget ide

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

<!-- end of auto-generated comment: Cypress test results  -->
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.

We have a lot of fixture files in our Cypress tests with DSLs of various
kinds. They are used to update the DSL using the
`/api/v1/layouts/{layoutId}/pages/{pageId}?applicationId={applicationId}`.

This API, is [in this line in
`LayoutControllerCE`](https://github.com/appsmithorg/appsmith/blob/c4e5d5e6c8f0428fe4a632333b9f6f13de3267b8/app/server/appsmith-server/src/main/java/com/appsmith/server/controllers/ce/LayoutControllerCE.java#L71),
and the request body is parsed as [objects of `LayoutUpdateDTO`
record](https://github.com/appsmithorg/appsmith/blob/71bc84fc76e85c49312659d18a7632ad62780583/app/server/appsmith-server/src/main/java/com/appsmith/server/dtos/LayoutUpdateDTO.java#L6).
This `record`, accepts _only_ the `dsl` field, and nothing else.

List of potential files that have this problem was identified with this
command:

```sh
cd app/client/cypress
rg -Io 'AddDsl\(".+?\)' \
  | cut -d\" -f2 \
  | sort -u \
  | while read line; do
    if rg -q '"(layoutOnLoadActions|layoutOnLoadActionErrors|userPermissions|new)":' fixtures/"$line".json; then
      echo $line
    fi
  done
```

(For reference, and to use on EE repo, after this is merged).

**/test all**

<!-- This is an auto-generated comment: Cypress test results  -->
> [!CAUTION]
> 🔴 🔴 🔴 Some tests have failed.
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9633990737>
> Commit: 9e848f1
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9633990737&attempt=1&selectiontype=test&testsstatus=failed&specsstatus=fail"
target="_blank">Cypress dashboard</a>.
> Tags: ``
> The following are new failures, please fix them before merging the PR:
<ol>
>
<li>cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor3_spec.ts
>
<li>cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor_1_spec.js
>
<li>cypress/e2e/Regression/ClientSide/Widgets/RTE/RichTextEditor_2_spec.js
</ol>
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/identified-flaky-tests-65890b3c81d7400d08fa9ee3?branch=master"
target="_blank">List of identified flaky tests</a>.

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



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

## Summary by CodeRabbit

- **Bug Fixes**
- Corrected the file path for loading DSL configuration in the nested
list widget scenario.

- **Chores**
- Streamlined multiple JSON files by removing deprecated
`layoutOnLoadActions` arrays and other obsolete fields, resulting in
cleaner and more manageable configurations.

<!-- 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, and extension to appsmithorg#34405.

This file's contents are used to call the endpoint:

```
/layouts/{layoutId}/pages/{pageId}?applicationId={applicationId}
```

But this endpoint accepts request payload as `LayoutUpdateDTO`, which
only has one single field, `dsl`, and nothing else.

But the way we use this JSON, is that we're sending the body as this:

```json
{
  "widgetName": "MainContainer",
  "backgroundColor": "none",
  "rightColumn": 1296,
  "snapColumns": 64,
  "detachFromLayout": true,
  "widgetId": "0",
  "topRow": 0,
  "bottomRow": 440,
  "containerStyle": "none",
  "snapRows": 125,
  "parentRowSpace": 1,
  "type": "CANVAS_WIDGET",
  "canExtend": true,
  "version": 47,
  "minHeight": 420,
  "parentColumnSpace": 1,
  "dynamicBindingPathList": [],
  "leftColumn": 0,
  "children": []
}
```

Not as this:
```json
{
  "dsl": {
    "widgetName": "MainContainer",
    "backgroundColor": "none",
    "rightColumn": 1296,
    "snapColumns": 64,
    "detachFromLayout": true,
    "widgetId": "0",
    "topRow": 0,
    "bottomRow": 440,
    "containerStyle": "none",
    "snapRows": 125,
    "parentRowSpace": 1,
    "type": "CANVAS_WIDGET",
    "canExtend": true,
    "version": 47,
    "minHeight": 420,
    "parentColumnSpace": 1,
    "dynamicBindingPathList": [],
    "leftColumn": 0,
    "children": []
  }
}
```

Which means that we aren't sending anything useful.


/test widget ide

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

<!-- end of auto-generated comment: Cypress test results  -->
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 Test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants