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

feat: add basic in-page feedback component #3841

Merged
merged 12 commits into from
Oct 28, 2024

Conversation

jamdelion
Copy link
Contributor

@jamdelion jamdelion commented Oct 23, 2024

This is currently just adding the first pass at the Feedback component in storybook.

Screenshot 2024-10-24 at 17 22 49

Next steps

In future PRs here are the todos:

  • Add in the Editor side
  • Form validation
  • Error handling

Links

Trello ticket: https://trello.com/c/jEOLoubW/3034-can-we-introduce-in-house-end-of-service-feedback?filter=member:johumphrey6

Figma design: https://www.figma.com/design/bnUUrsVRG6qPwDkTmVKACI/PlanX-Design?node-id=16904-1689&t=mx6FzCppbhIfPsBM-4

Copy link

github-actions bot commented Oct 23, 2024

Removed vultr server and associated DNS entries

@jamdelion jamdelion changed the title feat: in-page feedback component feat: add basic in-page feedback component Oct 24, 2024
@jamdelion jamdelion marked this pull request as ready for review October 24, 2024 16:41
Copy link
Contributor

@DafyddLlyr DafyddLlyr left a comment

Choose a reason for hiding this comment

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

Nice to see a Storybook first approach! 🙌

One small nit is that the hover shadows should match the border -

image

When it comes to the next steps of configuring the component, there's docs on this here.

@jamdelion jamdelion requested a review from DafyddLlyr October 28, 2024 12:32
Copy link
Contributor

@DafyddLlyr DafyddLlyr left a comment

Choose a reason for hiding this comment

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

One small little snag - getting some weird hover behaviour here. It looks like when I hover over the button group, the first item has a hover style applied. Can you recreate this?

Screen.Recording.2024-10-28.at.14.44.28.mov

@jamdelion
Copy link
Contributor Author

One small little snag - getting some weird hover behaviour here. It looks like when I hover over the button group, the first item has a hover style applied. Can you recreate this?

Screen.Recording.2024-10-28.at.14.44.28.mov

Nice catch, I'm seeing that on my side now as well! Will investigate... 👀

</Typography>

<Box pt={2} mb={3}>
<InputLabel label="How would you rate your experience with this service?" />
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The hover issue was caused by having more than one child inside the label component, as discussed in this issue: mui/material-ui#14543

I've made the children prop optional in the InputLabel component to get round this.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah nice one 👍

Alternatively, I think we could make children a ReactElement which would force a single element or fragment here. This will likely have cascading type issues but may point at other places where we're hitting a similar hover issue?

The a11y tests are still passing in CI and Storybook without the wrapping label, so this is all good as-is.

@jamdelion jamdelion requested a review from DafyddLlyr October 28, 2024 15:22
Copy link
Contributor

@DafyddLlyr DafyddLlyr left a comment

Choose a reason for hiding this comment

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

Perfect! Thanks for the quick fixes here.

@jamdelion jamdelion merged commit 18ac5a9 into main Oct 28, 2024
12 checks passed
@jamdelion jamdelion deleted the jh/feedback-component-refactoring branch October 28, 2024 16:42
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.

2 participants