docs: Populate Component Instance

[angelogulina]

Following up on this and this, I'm opening the Issue to help trace work and discussion about the Component Instance section.

[angelogulina]

Hi @afontcu, I'd like to start on this so asking for some guidance.

My idea for the initial approach would be to have these 3 sub items of Component Instance:

• port findComponent from V1 docs considering differences
• port props from V1 docs, considering differences

something like this:

Then 2 questions:

1. as far as I understand, the .vm part could be contained in the findComponent section?
2. anything else that would be nice to have (also fine to do it in a next Issue / PR)

Thanks!

[afontcu]

Hi!

Bear in mind that in VTU-next docs we're tying to focus on how to test stuff, instead of writing an API-centered documentation. This wasn't the case with VTU docs.

With that in mind, I would try to think of a use case were findComponent and props (and possibly .vm?) would make sense, and use the use case as a drive to showcase their use.

Does it sound OK to you? Any ideas?

btw:

Also why .vm is not available

AFAIK is no longer true :)

and yet another recommendation to test outputs instead of implementation details

this is still true 😉

[angelogulina]

Thanks for the guidance.

Sounds OK, sure. Don't have an idea on top of my head but I will find plenty I guess from the codebase I work on 😂

As soon as I have something, I'll push a draft and we can continue the discussion there.

[afontcu]

Hi @angelogulina! Just stopping by to see if you had something about this 😄

Cheers!

[angelogulina]

Hi @afontcu thanks for the ping. Still plan to write this one, yes but been really busy.

I'd tackle it around beginning of FEB if that works for you.