Hide ReadmeCard if backend returns 404

[fridajac]

Hey, I just made a Pull Request!

Changes:

• New function "isReadmeAvailable" is now exported from the Readme-plugin. This function return true or false based on if backend returns 404 error.
• EntitySwitch and EntitySwitch.Case has been added to the EntityPage in app.

Context

Our usability tests show that the EntityPage sometimes gets very cluttered with a lot of information. This results in that the users can't find what they are looking for. We want to fix this by making it possible to not render any ReadmeCard at all, if the README.md is not available (backend returns 404 Not Found).

Screenshots

Before

The "No README.md file found at source location"-text is displayed

After

No card is displayed

Checklist before requesting a review

• [x] I have performed a self-review of my own code
• [x] I have verified that the code builds perfectly fine on my local system
• [x] I have verified that my code follows the style already available in the repository
• [x] A changeset describing the change and affected packages. (more info)
• [x] Added or updated documentation
• [x] Tests for new functionality and regression tests for bug fixes
• [x] Screenshots attached (for UI changes)

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: a790550f8e44a1fb2b368d7f089fa4075c9399f4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

| Name | Type | | ------------------------------------- | ----- | | @axis-backstage/plugin-readme-backend | Minor | | @axis-backstage/plugin-readme | Minor | | app | Minor | | backend | Patch |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[fridajac]

LGTM, another way to solve this would be to create an async "haveReadme" function and have the EntitySwitch handle the show/hide logic. Would probably need another (cached) api call.

<EntitySwitch.case if={haveReadme}

That is much better! Thanks!