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

chore: organize ws stats, schedule stories #1790

Merged
merged 3 commits into from
May 26, 2022

Conversation

greyscaled
Copy link
Contributor

@greyscaled greyscaled commented May 26, 2022

Resolves: #1681

Summary:

  • Moves WorkspaceSchedule out of WorkspaceStats
  • Adds WorkspaceScheduleForm directory
  • Adds meaningful stories for WorkspaceStats (removed in 4f2ad13)

Impact:

Improves breadth of our chromatic visual regression tests since the
examples for WorkspaceStats were non-representative of the component

Resolves: #1681

Summary:

- Moves WorkspaceSchedule out of WorkspaceStats
- Adds WorkspaceScheduleForm directory
- Adds meaningful stories for WorkspaceStats

Impact:

Improves breadth of our chromatic visual regression tests since the
examples for WorkspaceStats were non-representative of the component
@greyscaled greyscaled requested a review from a team as a code owner May 26, 2022 17:15
@greyscaled greyscaled self-assigned this May 26, 2022
Copy link
Collaborator

@BrunoQuaresma BrunoQuaresma left a comment

Choose a reason for hiding this comment

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

LGTM

@presleyp
Copy link
Contributor

Looks great! Just wondering, do you think we need the separate WorkspaceStats stories, given the Workspace ones?

@greyscaled
Copy link
Contributor Author

greyscaled commented May 26, 2022

Looks great! Just wondering, do you think we need the separate WorkspaceStats stories, given the Workspace ones?

Great question! I think it's ok to have the stories at the granular level and composed level, especially if we say add props to WorkspaceStats that make it re-usable in a different view. An example that comes to mind is some view whereby an admin is looking at details about someone else's Workspace way down the road in the EE world.

@greyscaled
Copy link
Contributor Author

I'll remove them from now, to clear things up a bit --> just I don't have a satisfying answer on what granules to storybook just yet. Hmm. 🤔

@greyscaled greyscaled merged commit 7467bfe into main May 26, 2022
@greyscaled greyscaled deleted the vapurrmaid/gh-1681/fix-storybook branch May 26, 2022 20:14
kylecarbs pushed a commit that referenced this pull request Jun 10, 2022
Resolves: #1681

Summary:

- Moves WorkspaceSchedule out of WorkspaceStats
- Adds WorkspaceScheduleForm directory

Impact:

Improves breadth of our chromatic visual regression tests since the
examples for WorkspaceStats were non-representative of the component
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.

Fix storybooking of workspace schedule
3 participants