Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Differentiate between versioned components #25

Open
cgreene-st opened this issue Sep 29, 2021 · 0 comments
Open

Differentiate between versioned components #25

cgreene-st opened this issue Sep 29, 2021 · 0 comments

Comments

@cgreene-st
Copy link

Hey,

I read your blog and found it very interesting, which led me here.

I do have a question, and maybe it's not the right forum but thought you might be able to shed some light on you solved it.

On the dashboard that you created that's driven by this data, you are able to show adoption from v3 to v4. Looking back through the tags on this repo, it doesn't look like the structure changed from version to version. So my question, is how did you report on that from v3 to v4 comparison. Maybe a more solid example might help:

So in Evergreen v3 you have a button

import { Button } from 'evergreen-ui'

and in Evergreen v4 you also have the same import

import { Button } from 'evergreen-ui'

Running the report won't give you any information around which version the button belongs. Obviously if it had a different package path, that would be a differentiator. Just trying to understand how you might have solved that. We have a similar set up, the real gold in this is seeing the adoption rate of v3 vs v4.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant