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

Create a StudioError component and use it instead of alerts with severity #13391

Closed
JamalAlabdullah opened this issue Aug 19, 2024 · 2 comments · Fixed by #13412
Closed

Create a StudioError component and use it instead of alerts with severity #13391

JamalAlabdullah opened this issue Aug 19, 2024 · 2 comments · Fixed by #13412
Labels
added-to-sprint kind/chore text/content used for issues that need som text improvements, often by ux

Comments

@JamalAlabdullah
Copy link
Contributor

JamalAlabdullah commented Aug 19, 2024

We created this issue based on ref

  • We need to create a new componenet StudioError
  • Replace alle alerts severity=danger with StudioError
@JamalAlabdullah JamalAlabdullah added kind/chore status/triage text/content used for issues that need som text improvements, often by ux added-to-sprint labels Aug 19, 2024
@JamalAlabdullah JamalAlabdullah self-assigned this Aug 19, 2024
@framitdavid
Copy link
Collaborator

@JamalAlabdullah do we need to create a new one or can we rename this one and used that instead? https://github.com/Altinn/altinn-studio/blob/main/frontend/libs/studio-components/src/components/StudioPageError/StudioPageError.tsx 😊

@JamalAlabdullah
Copy link
Contributor Author

@framitdavid I will answer in Slack for a quick discussion. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
added-to-sprint kind/chore text/content used for issues that need som text improvements, often by ux
Projects
Archived in project
4 participants