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

Users/mordvinx/testplane 404.new UI error boundaries #630

Conversation

mordvinx
Copy link
Contributor

@mordvinx mordvinx commented Jan 20, 2025

Added ErrorHandler components, which prevents app from crashing to white screen.

A small passing refactor was executed.

Copy link
Member

@shadowusr shadowusr left a comment

Choose a reason for hiding this comment

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

Отличный шаг в сторону более стабильного UX! Круто, что покрыто столько кейсов, мне понравилось! 🔥

Есть ряд вопросов насчет расхождений с макетами, предлагаю обсудить в комментах.

@mordvinx
Copy link
Contributor Author

@shadowusr можно смотреть

Copy link
Member

@shadowusr shadowusr left a comment

Choose a reason for hiding this comment

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

В целом критичных замечаний нет, написал несколько моментов по дизайну и хотелось бы разобраться зачем нужны watchFor+restore

@mordvinx
Copy link
Contributor Author

@shadowusr можно отсматривать, оставшиеся комменты жду от тебя резолв либо дополнения

Copy link
Member

@shadowusr shadowusr left a comment

Choose a reason for hiding this comment

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

Помимо опечаток больше замечаний нет

@mordvinx mordvinx merged commit f92dee5 into gemini-testing:master Jan 24, 2025
4 checks passed
@mordvinx mordvinx deleted the users/mordvinx/TESTPLANE-404.new-ui-error-boundaries branch January 24, 2025 11:06
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