- Issue created by @bnjmnm
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
💯 — this will massively improve the quality of bug reports, too!
Hence tagging this .
Please find the attached video demonstrating the steps to reproduce the "An unexpected error has occurred while fetching the layout" issue.
- 🇺🇸United States bnjmnm Ann Arbor, MI
Please find the attached video demonstrating the steps to reproduce the "An unexpected error has occurred while fetching the layout" issue
This is helpful, but just to make things clear, the above is just one of many ways trigger this message. The ""An unexpected error..." is a generic message in the UI that could be triggered by any number of different errors. Detailed, helpful info already exists in the JS console, too! This issue is about bringing those details to the UI
- 🇺🇸United States effulgentsia
The sooner we do this, the sooner we get to reap the benefits, but I don't see why we should block a 1.0.0 release on it. Seems like the kind of thing that could non-disruptively go into 1.1.0 or even 1.0.1. Therefore re-tagging from "stable blocker" to "stable target".
