Skip to content

Conversation

@julieg18
Copy link
Contributor

@julieg18 julieg18 commented May 15, 2023

Demo

Screen.Recording.2023-05-17.at.3.57.26.PM.mov
image

Part of #3434

@julieg18 julieg18 added the product PR that affects product label May 15, 2023
@julieg18 julieg18 self-assigned this May 15, 2023
version: '1.0.0'
},
hasData: false,
isAboveLatestTestedVersion: false,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned by Stephanie a couple prs ago, we need to stop our tests from writing SetupData from scratch for every test. In #3434 and will work on this in our next sprint!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have also run into this. My changes will conflict. I can do this today.

shareLiveToStudio: false
})

const iconWrapper = screen.getAllByTestId('info-tooltip-toggle')[0]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed array selection was being used in info icon tests which is bad practice since the setup order will eventually change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I have run into this as well

title="DVC"
isSetup={isDvcSetup}
icon={getDvcStatusIcon(isDvcSetup, !!isAboveLatestTestedVersion)}
secondaryTooltipText={
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2023-05-16 at 8 55 58 AM

Message is pretty lengthy. Maybe we could simplify it or remove the summary text about the DVC section 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could easily remove "Warning" from the text as the icon already states that there is a warning present. Also, there should be a comma before "which".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Message is pretty lengthy. Maybe we could simplify it or remove the summary text about the DVC section

Yes and yes. However, I think we need to update a bit. The desired behaviour is if the user is getting unexpected behaviour then they should first try to upgrade the extension and if that is not possible downgrade the CLI. Here is a rough attempt at improving the message.

The located version has not been tested against the extension. 
If you are experiencing unexpected behaviour first try to update the extension. 
If there are no updates available then please downgrade DVC to the same minor version as displayed.

That can be polished but it is a start. Make sense?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense! Here's what I've got so far:

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@julieg18 julieg18 marked this pull request as ready for review May 16, 2023 14:02
@julieg18 julieg18 requested review from mattseddon and sroy3 as code owners May 16, 2023 14:02
@julieg18 julieg18 requested a review from shcheklein May 16, 2023 14:02
title="DVC"
isSetup={isDvcSetup}
icon={getDvcStatusIcon(isDvcSetup, !!isAboveLatestTestedVersion)}
secondaryTooltipText={
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could easily remove "Warning" from the text as the icon already states that there is a warning present. Also, there should be a comma before "which".

icon?: TooltipIconType
}>
> = ({ icon = TooltipIconType.INFO, sectionKey, children }) => {
const infoIcon = (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[N] I think leaving this named infoIcon is misleading because it is no longer always the information icon. Maybe indicatorIcon would be a better name.

Copy link
Contributor Author

@julieg18 julieg18 May 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! We actually use the term info in multiple places regarding the component. Data id, component name, class, etc. I'll rename the different places in a followup :)

title="DVC"
isSetup={isDvcSetup}
icon={getDvcStatusIcon(isDvcSetup, !!isAboveLatestTestedVersion)}
secondaryTooltipText={
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Message is pretty lengthy. Maybe we could simplify it or remove the summary text about the DVC section

Yes and yes. However, I think we need to update a bit. The desired behaviour is if the user is getting unexpected behaviour then they should first try to upgrade the extension and if that is not possible downgrade the CLI. Here is a rough attempt at improving the message.

The located version has not been tested against the extension. 
If you are experiencing unexpected behaviour first try to update the extension. 
If there are no updates available then please downgrade DVC to the same minor version as displayed.

That can be polished but it is a start. Make sense?

shareLiveToStudio: false
})

const iconWrapper = screen.getAllByTestId('info-tooltip-toggle')[0]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I have run into this as well

version: '1.0.0'
},
hasData: false,
isAboveLatestTestedVersion: false,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have also run into this. My changes will conflict. I can do this today.

@julieg18 julieg18 enabled auto-merge (squash) May 18, 2023 13:41
@qlty-cloud-legacy
Copy link

Code Climate has analyzed commit b9368ed and detected 3 issues on this pull request.

Here's the issue category breakdown:

Category Count
Duplication 3

The test coverage on the diff in this pull request is 100.0% (85% is the threshold).

This pull request will bring the total coverage in the repository to 95.0% (0.0% change).

View more on Code Climate.

@julieg18 julieg18 merged commit 30935d8 into main May 18, 2023
@julieg18 julieg18 deleted the add-dvc-setup-latest-tested-version-warning branch May 18, 2023 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product PR that affects product

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants