The PageInfo component triggers the highest-level error boundary in the app if a problem while fetching data occurs. This means that the entire app becomes unusable when that happens.
This is easy to observe in #3523029: Content entity form: URL alias without leading slash should be prevented by client-side validation. While that issue and potential successors will ensure such error never occurs in the server, we need to account for any errors.
Display an error inside the panel that PageInfo opens if fetching the data was not successful for any reason. Ensure the app remains usable.
By quickly reusing the ErrorCard component we have, we can have:
| Comment | File | Size | Author |
|---|---|---|---|
| xb-page-info-error-card.jpg | 62.02 KB | balintbrews |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
balintbrewsComment #6
jessebaker commentedMerged!