fix(313) - Kamelets in Camel Routes are not handled properly

[shivamG640]

Fixes #313

Now, when we replace the source node, the catalog page loads like this:

Similarly, the Catalog page looks like this when we replace the last node:

[lordrip]

The conditions look good 👌

Do you think it would be possible to add a test for this method in the camel-route.test.ts file?

Certainly, we would need to have a mock for the catalog but it's not available yet, so we could create 3 scenarios and assert that we get a function on each of them, after that, once we have the catalog mock, we can do better assertions against the real tiles.

[lordrip]

The structure could be:

  describe('getCompatibleComponents')
    it(`scenario for from`)
    it(`scenario for InsertSpecialChil`)
    it(`remaining scenario`)

note the messages are simply placeholder, we would need a description that explains the test case appropriately

[shivamG640]

I get it. I'll try to add those tests in some time!

[shivamG640]

@lordrip Do you mean something like this ?

[lordrip]

Yes, that's a good start, but remember to provide a descriptive name for the it.

• it('should not provide isProducerOnly components')
• it('should provide components')
• it('should provide processors')
• it('should provide source kamelets')

[lordrip]

Then the assertion would be to receive a function out of the getCompatibleComponents method. Later on, when we provide a catalog mock, we'll change those assertions to something more specific, by testing which components we get in response.

[shivamG640]

Hi @lordrip ,
I wrote a few tests as per my understanding of the code. Let me if this is something you were looking for or we can discuss changing this!

[shivamG640]

Hi @lordrip ,
Thanks for your comments, I added those changes.
I'll merge it once you review it again!

[lordrip]

Thanks @shivamG640 , looks good 👍