[Devcontainers frontend plugin] Make the component hidden if no annotation is present
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in packages/app/src/components/catalog/EntityPage.tsx and inspect the DevcontainersProvider EntitySwitch case, along with the existing DEVCONTAINERS_ANNOTATION and isDevContainersAvailable references. Done means the component is hidden when the annotation is absent and remains visible when the correct annotation is present.
Written by the indexing model from the issue text.
Description
If the annotation is not present, make the DevcontainersProvider component hidden.
This should be working in packages/app/src/components/catalog/EntityPage.tsx:
<EntitySwitch>
<EntitySwitch.Case if={isDevContainersAvailable}>
<Grid item md={6} xs={12}>
<DevcontainersProvider config={devcontainersConfig}>
<ExampleDevcontainersComponent/>
</DevcontainersProvider>
</Grid>
</EntitySwitch.Case>
</EntitySwitch>
The isDevContainersAvailavble function should check if the correct annotations are in place like (pseudocode):
export const isDevContainersAvailable = (entity: Entity) =>
Boolean(entity.metadata.annotations?.[DEVCONTAINERS_ANNOTATION]);
This way the item can be hidden and the page can be cleaner.
- Dominant language
- TypeScript
- Stars
- 67
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/backstage-plugins
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
coder/backstage-plugins#105 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
coder/backstage-plugins#148 ·
-
Coder plugin: Fallback authentication button still appears after user has already authenticated Openbug
coder/backstage-plugins#146 · 1 assignee ·
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
coder/backstage-plugins#144 · 1 comment ·
-
bug
coder/backstage-plugins#142 · 7 comments · 1 assignee ·
All issues in coder/backstage-plugins
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·