Reporting environment issues #213
Conversation
|
Just went briefly through the changes, and I noticed we don't have a I just wanted to confirm whether this is indeed the case or there is a different reason why we are going to a manual matching. |
I thought about this and decided it would probably make more sense for environment issues to be across architectures. So you are right. For instance, a broken machine is broken regardless of the architecture. |
omar-selo
force-pushed
the
reporting-environment-issues
branch
from
5b7d69c
to
dbaf6a2
Compare
There was a problem hiding this comment.
Can we maybe make the TestCaseIsueePreloader a generic ReportedIssuesPreloader that will watch for both providers, it seems like we are repeating most of the code.
There was a problem hiding this comment.
Inspired by this comment, I refactored most loading of providers into two widgets: NonBlockingProviderPreloader and BlockingProviderRreloader.
There was a problem hiding this comment.
How can you not love a code clean-up 😄
| return Expandable( | ||
| title: const Text('Event Log'), | ||
| initiallyExpanded: initiallyExpanded, | ||
| children: <Widget>[ | ||
| testEvents.when( |
There was a problem hiding this comment.
Aren't we deleting the Expandable here, I don't see it anywhere in the new code
There was a problem hiding this comment.
I tried manually testing everything now, so hopefully I didn't miss anything else
Description
Adds ability to report environment issues.
Resolved issues
Resolves https://warthogs.atlassian.net/browse/RTW-353
Documentation
Web service API changes
Adds new endpoint
/v1/environments/reported-issueswith GET, POST, PUT, and DELETE.Tests
Added automated tests to the backend.
Manually tested the front-end. See video below:
Screencast from 2024-09-17 14-05-03.webm