Skip to content
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

Add an indeterminate linear progress bar #3429

Merged
merged 45 commits into from
Jul 8, 2024

Conversation

JoanaMMoreira
Copy link
Contributor

@JoanaMMoreira JoanaMMoreira commented May 15, 2024

Add indeterminate variant to LinearProgress

#3354

Copy link

vercel bot commented May 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
saltdesignsystem ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 8, 2024 2:09pm

Copy link

changeset-bot bot commented May 15, 2024

🦋 Changeset detected

Latest commit: 2533ded

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@salt-ds/core Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

@origami-z origami-z left a comment

Choose a reason for hiding this comment

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

Do we need a site doc example update?

Otherwise looks good

.changeset/four-bugs-reply.md Outdated Show resolved Hide resolved
@JoanaMMoreira
Copy link
Contributor Author

Do we need a site doc example update?

Otherwise looks good

I've updated the original example but I'm not sure if it should be separate? Will need some wording around it if that's the case

@origami-z
Copy link
Contributor

I've updated the original example but I'm not sure if it should be separate? Will need some wording around it if that's the case

I think we need some extra design guidance on when to use and avoid. maybe MUI would have something to get us started

Copy link
Contributor

@joshwooding joshwooding left a comment

Choose a reason for hiding this comment

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

Left a few comments. but we should also show going from an indeterminate to a determinate progress bar.

@JoanaMMoreira
Copy link
Contributor Author

Left a few comments. but we should also show going from an indeterminate to a determinate progress bar.

Do you mean having an example that toggles between those two states?

@joshwooding
Copy link
Contributor

Left a few comments. but we should also show going from an indeterminate to a determinate progress bar.

Do you mean having an example that toggles between those two states?

We need an example that shows a realistic use-case.

Copy link
Contributor

@joshwooding joshwooding left a comment

Choose a reason for hiding this comment

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

Just marking it as needs changes to make it clear

@JoanaMMoreira
Copy link
Contributor Author

Left a few comments. but we should also show going from an indeterminate to a determinate progress bar.

Do you mean having an example that toggles between those two states?

We need an example that shows a realistic use-case.

@navkaur76 any thoughts on the best example for this?

origami-z
origami-z previously approved these changes Jun 3, 2024
@joshwooding joshwooding force-pushed the indeterminate-linear-progress-bar branch from 80f55e2 to 2533ded Compare July 8, 2024 14:03
@joshwooding joshwooding changed the title Indeterminate linear progress bar Add an indeterminate linear progress bar Jul 8, 2024
@origami-z origami-z merged commit 8b43adf into main Jul 8, 2024
15 checks passed
@origami-z origami-z deleted the indeterminate-linear-progress-bar branch July 8, 2024 16:00
@@ -43,8 +45,8 @@ export const LinearProgress = forwardRef<HTMLDivElement, LinearProgressProps>(
hideLabel = false,
max = 100,
min = 0,
value = 0,
Copy link
Contributor

Choose a reason for hiding this comment

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

is this considered a breaking change ?
Should we leave this as 0 and opt into indeterminate ?
At some point a breaking change release we could make this the default ?

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

Successfully merging this pull request may close these issues.

6 participants