TT-6878 Navigating home after team deletion on that team's page #115
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added a new renderer instructions file to guide agents through the architecture and startup flow of the app. - Implemented the ProjectsScreen and TeamsScreen components with responsive layouts and mobile-friendly interactions. - Created utility functions for route management and navigation, enhancing the user experience across devices. - Split the old home screen into two pages, where the latter (viewing a team's projects) is now considered "home"
- logic to go to team screen - desktop projects and team screen - responsive layout for projects screen on desktop - allow user to access original functions on desktop - fix some css issues on desktop
- Added a new renderer instructions file to guide agents through the architecture and startup flow of the app. - Implemented the ProjectsScreen and TeamsScreen components with responsive layouts and mobile-friendly interactions. - Created utility functions for route management and navigation, enhancing the user experience across devices. - Split the old home screen into two pages, where the latter (viewing a team's projects) is now considered "home" - TT-6860 update GPT5 logic - TT-6813 fix card styles (sillsdev#80) - Cleaning up some temp items in an effort to bring Teams and Projects to a unified experience on desktop and mobile - Adding Edit Workflow for desktop - Update memory preferences for response guidelines and automated browser usage - Show Members button and dialog on Projects screen - Updated strings
Refactored confirmation dialog into TeamDialog to remove duplication. And removed unused ref to TeamDialog.
sarahentzel
reviewed
Nov 19, 2025
| setExitAlert(true); | ||
| } | ||
| const queueLength = remote?.requestQueue.length ?? 0; | ||
| const queueLength = 0; |
Collaborator
There was a problem hiding this comment.
Please explain or revert this change.
Contributor
Author
There was a problem hiding this comment.
It's failing the Husky build such that I couldn't check in. Red-lining the IDE as well
Contributor
Author
There was a problem hiding this comment.
I didn't see it defined anywhere, though I must admit I didn't look outside the file. Maybe it's something from a newly added package and I need to run npm i?
Collaborator
There was a problem hiding this comment.
remote.requestQueue is used in many places. You can't just change logic because it's inconvenient to you. Revert the change and figure out how to get it to compile please.
Contributor
Author
There was a problem hiding this comment.
I checked again this morning. Same behavior
sarahentzel
reviewed
Nov 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactored confirmation dialog into TeamDialog to remove duplication. And removed unused ref to TeamDialog.