- Issue created by @tedbow
- First commit to issue fork.
- @phenaproxima opened merge request.
- Status changed to Needs review
almost 2 years ago 7:01pm 6 February 2023 - πΊπΈUnited States tedbow Ithaca, NY, USA
@phenaproxima did you check the other place mentioned in Proposed resolution 2)?
- Status changed to Needs work
almost 2 years ago 9:49pm 6 February 2023 - πΊπΈUnited States tedbow Ithaca, NY, USA
Looks good but I don't the original problem documented in the screenshot has test coverage.
This is when the User is on the UpdateReady form and there is a status check warning with 1 message and summary.
the closest test coverage we have is \Drupal\Tests\automatic_updates\Functional\UpdateWarningTest but it only deals with an warning with more than 1 message, that is why it was passing.
That should be update to handle both cases. I think just setting a different `TestSubscriber::setTestResult([$warning], StatusCheckEvent::class);` and reloading the page should be ok
- Status changed to Needs review
almost 2 years ago 2:38pm 7 February 2023 - πΊπΈUnited States phenaproxima Massachusetts
Crediting you for review.
- Status changed to Needs work
almost 2 years ago 12:58pm 8 February 2023 - π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
π€― This is such a no-brainer improvement. This explains why I've gotten confused in the past by the assertions in the build tests π
But β¦ there's still something that I don't quite get: why we sometimes want only the summary, and not also the non-summarized messages?
- Status changed to Needs review
almost 2 years ago 2:26pm 8 February 2023 - πΊπΈUnited States phenaproxima Massachusetts
why we sometimes want only the summary, and not also the non-summarized messages?
As I understand it:
On the status report, and on the updater form, we want everything. Summaries and details. These areas are where the user is most concerned with the details, and could use as much information as possible to fix the problems.
On any other admin page, we want only the summaries (or first message, if there is no summary). In such a context, we just want people to know that problems exist, and give people a basic idea of what those problems are. But providing the full details would be clutter.
Not seeing any other actionable feedback here, so this is back to needing review...
- Assigned to phenaproxima
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
On any other admin page (like /admin/structure and friends), we want only the summaries (or first message, if there is no summary). In such a context, we just want people to know that problems exist, and give people a basic idea of what those problems are. But providing the full details would be clutter.
But how do we expect people to act on problems surfaced in the status report if they literally cannot see the details? π
- πΊπΈUnited States phenaproxima Massachusetts
They can see the details on the status report...? (By "status report", by the way, I'm referring specifically to /admin/reports/status.)
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
That's not what I'm seeing in
StatusCheckTest
β see https://git.drupalcode.org/project/automatic_updates/-/merge_requests/68....I verified locally by doing
var_dump($expected_results['1 error']); var_dump($this->getSession()->getPage()->getContent()); return;
immediately after that.
What am I missing? π
- πΊπΈUnited States phenaproxima Massachusetts
The fact that the result you're looking at only has one message. In which case, that's the only thing that gets displayed.
If I add the following code to the end of ComposerExecutableValidator:
$event->addError([ 'One message with some details.', 'Another message with some details.', ], t('A test summary'));
I get this on the status report:
Which is exactly what I would expect to see.
- Issue was unassigned.
- Status changed to RTBC
almost 2 years ago 3:04pm 9 February 2023 - π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
OMG β I must've missed that then in my detailed test π Sorry for the distraction!
-
tedbow β
committed 5f652d45 on 8.x-2.x authored by
phenaproxima β
Issue #3339657 by phenaproxima, tedbow: Always show summary of...
-
tedbow β
committed 5f652d45 on 8.x-2.x authored by
phenaproxima β
- Status changed to Fixed
almost 2 years ago 5:17am 10 February 2023 Automatically closed - issue fixed for 2 weeks with no activity.