Skip to content

Commit

Permalink
chore: fix Camel 4.9.0 tests
Browse files Browse the repository at this point in the history
  • Loading branch information
@lordrip @igarashitm
lordrip authored and igarashitm committed Dec 9, 2024
1 parent bafb9c1 commit 4417f26
Show file tree
Hide file tree
Showing 2 changed files with 29 additions and 13 deletions.
4 changes: 2 additions & 2 deletions packages/ui/src/components/Form/dataFormat/DataFormatEditor.test.tsx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ describe('DataFormatEditor', () => {
fireEvent.change(inputElement, { target: { value: 'json' } });
});
dropdownItems = screen.getAllByTestId(/dataformat-dropdownitem-.*/);
expect(dropdownItems).toHaveLength(3);
expect(dropdownItems).toHaveLength(4);
});

it('should clear filter and close the dropdown with close button', async () => {
Expand All @@ -174,7 +174,7 @@ describe('DataFormatEditor', () => {
fireEvent.change(inputElement, { target: { value: 'json' } });
});
let dropdownItems = screen.getAllByTestId(/dataformat-dropdownitem-.*/);
expect(dropdownItems).toHaveLength(3);
expect(dropdownItems).toHaveLength(4);
const clearButton = screen.getByLabelText('Clear input value');
await act(async () => {
fireEvent.click(clearButton);
Expand Down
38 changes: 27 additions & 11 deletions ...els/visualization/flows/support/__snapshots__/camel-component-schema.service.test.ts.snap
View file
Original file line number Diff line number Diff line change
Expand Up @@ -303,13 +303,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -656,13 +656,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -860,6 +860,14 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"title": "Backoff Multiplier",
"type": "integer",
},
"browseLimit": {
"default": 100,
"deprecated": false,
"description": "Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited.",
"group": "advanced",
"title": "Browse Limit",
"type": "integer",
},
"bufferSize": {
"default": 131072,
"deprecated": false,
Expand Down Expand Up @@ -1449,13 +1457,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -1561,6 +1569,14 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should build the a
"title": "Bridge Error Handler",
"type": "boolean",
},
"browseLimit": {
"default": 100,
"deprecated": false,
"description": "Maximum number of messages to keep in memory available for browsing. Use 0 for unlimited.",
"group": "advanced",
"title": "Browse Limit",
"type": "integer",
},
"bufferSize": {
"default": 131072,
"deprecated": false,
Expand Down Expand Up @@ -2243,13 +2259,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should not build a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -2436,13 +2452,13 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should transform a
"type": "string",
},
"variableReceive": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using receive variable then the received body is stored only in this variable and not on the current message.",
"group": "common",
"title": "Variable Receive",
"type": "string",
},
"variableSend": {
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current Message , however the headers from the Message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down Expand Up @@ -2587,7 +2603,7 @@ exports[`CamelComponentSchemaService getVisualComponentSchema should transform a
"type": "string",
},
"variableSend": {
"description": "To use a variable to store the received message body (only body, not headers). This is handy for easy access to the received message body via variables. Important: When using receive variable then the received body is stored only in this variable and not on the current org.apache.camel.Message .",
"description": "To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to easily control what data to use for sending and receiving. Important: When using send variable then the message body is taken from this variable instead of the current message, however the headers from the message will still be used as well. In other words, the variable is used instead of the message body, but everything else is as usual.",
"group": "common",
"title": "Variable Send",
"type": "string",
Expand Down

0 comments on commit 4417f26

Please sign in to comment.