-
Notifications
You must be signed in to change notification settings - Fork 21
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(Catalog): Add RouteConfiguration related entities #1012
feat(Catalog): Add RouteConfiguration related entities #1012
Conversation
ef2d88a
to
df8f17b
Compare
@@ -366,7 +366,7 @@ describe('Camel Route', () => { | |||
const logWhenNode = whenNode?.getChildren()?.[0]; | |||
expect(logWhenNode).toBeDefined(); | |||
expect(logWhenNode!.data.path).toEqual('from.steps.1.choice.when.0.steps.0.log'); | |||
expect(logWhenNode!.getNodeLabel()).toEqual('log'); | |||
expect(logWhenNode!.getNodeLabel()).toEqual('log-1'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am baffled by this one....the test label says "should use uri as label" but here it seems we check for an id?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mmm, suspicious, I'll check again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, the test is to check that all nodes are creted properly. This particular expectation is checking the node's label and since this change, for a processor, the label algorithm goes like this:
- Description
- Id
- Component name
case 'to':
case 'toD':
return uriString ?? id ?? camelElementLookup.processorName;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I see. the test description was a bit misleading
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reworked this section to only show IDs as a fallback for entities, like intercept*
, errorHandler
and onException
As a prerequisite of KaotoIO#492, we need to add the related entities to the catalog. This commit adds the following entities: * intercept * interceptFrom * interceptSendToEndpoint * onException * onCompletion In addition to that, we also show the entity ID if provided in case there's no description available. relates: KaotoIO#492
df8f17b
to
d42e30d
Compare
Context
As a prerequisite of #492, we need to add the related entities to the catalog.
This commit adds the following entities:
In addition to that, we also show the entity ID if provided in case there's no description available.
Note
These entities will be available in an upcoming PR when the
RouteConfiguration
visual entity class is introduced.relates: #492