You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution description:
Moved the CustomDrawer component from packages/app to plugins/lightspeed/dev to resolve workspace accessibility issues during development. This ensures the component is directly available to the dev plugin without relying on the app workspace package
✔️ Checklist
A changeset describing the change and affected packages. (more info)
Added or Updated documentation
Tests for new functionality and regression tests for bug fixes
Move CustomDrawer component to lightspeed plugin dev
🐞 Bug fix
Walkthroughs
Description
• Moved CustomDrawer component from packages/app to plugins/lightspeed/dev
• Updated import paths to reference component from lightspeed plugin
• Added @internal JSDoc annotations to mark component as internal API
• Exported CustomDrawer via plugin's dev entry point in package.json
• Updated dependency reference to use workspace protocol
Diagram
flowchart LR
A["packages/app<br/>CustomDrawer.tsx"] -->|"moved to"| B["plugins/lightspeed/dev<br/>CustomDrawer.tsx"]
C["ApplicationDrawer.tsx<br/>import path"] -->|"updated to"| D["@red-hat-developer-hub/<br/>backstage-plugin-lightspeed/dev"]
E["DrawerComponent.tsx<br/>import path"] -->|"updated to"| D
F["package.json<br/>exports"] -->|"added dev entry"| D
• Updated import statement to reference CustomDrawer from lightspeed plugin dev export
• Changed from local relative import to plugin package import path
View more (4) 4. workspaces/lightspeed/plugins/lightspeed/dev/CustomDrawer.tsx
✨ Enhancement +6/-2
Add internal API annotations to CustomDrawer
• Removed eslint disable/enable comments for restricted imports
• Added @internal JSDoc annotations to CustomDrawerProps type and CustomDrawer component
• Maintained all existing component functionality and props
• Updated import to use local CustomDrawer from same dev directory
• Removed cross-monorepo relative import that violated import restrictions
• Simplified import path from packages/app to local dev folder
1. Changeset includes private app 🐞 Bug⛯ Reliability
Description
The added changeset declares a release for the private app package, but repo CI explicitly rejects
changesets that include private workspace packages (including app), so this PR will fail changeset
verification.
The changeset explicitly lists 'app': patch. The repository has a CI verification script that
treats app as a private package and exits with failure if any changeset includes releases for
private packages.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The changeset `soft-yaks-hope.md` includes a release for `app`, which is a private workspace package. CI runs `scripts/ci/verify-changesets.js` and fails if a changeset includes any private package releases.
## Issue Context
- `app` is marked `private: true`.
- CI explicitly rejects changesets containing releases for `app`.
## Fix Focus Areas
- workspaces/lightspeed/.changeset/soft-yaks-hope.md[1-4]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
2. No typesVersions for dev 🐞 Bug✓ Correctness
Description
A new subpath export @…/dev was added but there is no corresponding typesVersions mapping, which
can break TypeScript consumers that rely on typesVersions rather than exports for subpath type
resolution.
The package now exports ./dev, but typesVersions only maps alpha and package.json. This
inconsistency can lead to Cannot find module '@…/dev' or its corresponding type declarations in TS
setups that use typesVersions for subpath resolution (a pattern already used for alpha in this
repo).
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The package exports a new subpath (`./dev`) but does not include a corresponding `typesVersions` mapping. Some TS configurations use `typesVersions` for subpath type resolution and may fail to resolve `@red-hat-developer-hub/backstage-plugin-lightspeed/dev`.
## Issue Context
This repo already maintains `typesVersions` for `alpha`, suggesting subpath compatibility is expected.
## Fix Focus Areas
- workspaces/lightspeed/plugins/lightspeed/package.json[10-25]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
3. Dev code used by app 🐞 Bug⛯ Reliability
Description
The app now imports CustomDrawer from the plugin’s ./dev export; this couples production app
code to a dev-folder module and risks publish/packaging mismatches or accidental external
consumption of an unstable/internal API.
+import { CustomDrawer } from '@red-hat-developer-hub/backstage-plugin-lightspeed/dev';
Evidence
ApplicationDrawer imports from @…/dev, which is backed by an export pointing at
./dev/CustomDrawer.tsx. That module is annotated @internal, but package.json exports still
makes it an official import path. Additionally, the package’s files list does not mention dev/,
so unless the prepack/build tooling accounts for this new export, the published artifact may not
contain the referenced file.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The Backstage app (`packages/app`) now imports `CustomDrawer` from the plugin’s `./dev` export. This makes app runtime depend on a dev-folder module and exposes an `@internal` component via package `exports`.
## Issue Context
- `./dev` is now a public subpath in `exports`.
- The component is marked `@internal` but still importable.
- Packaging may not include `dev/` unless explicitly handled.
## Fix Focus Areas
- workspaces/lightspeed/packages/app/src/components/Root/ApplicationDrawer.tsx[17-26]
- workspaces/lightspeed/plugins/lightspeed/package.json[10-15]
- workspaces/lightspeed/plugins/lightspeed/package.json[96-101]
- workspaces/lightspeed/plugins/lightspeed/dev/CustomDrawer.tsx[22-40]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
+---+'@red-hat-developer-hub/backstage-plugin-lightspeed': patch+'app': patch+---++Moved the `CustomDrawer` component from `packages/app` to `plugins/lightspeed/dev` to resolve workspace accessibility issues during development.
Evidence
Workspace lint-staged/prettier is configured to rewrite *.md files, which typically enforces a
trailing newline; the diff explicitly indicates the file has no newline at EOF.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The changeset file is missing a trailing newline, which can fail formatting checks.
## Issue Context
This workspace runs prettier over `*.md` via lint-staged.
## Fix Focus Areas
- workspaces/lightspeed/.changeset/soft-yaks-hope.md[1-6]
- workspaces/lightspeed/package.json[65-72]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
ⓘ The new review experience is currently in Beta. Learn more
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey, I just made a Pull Request!
Resolves:
https://issues.redhat.com/browse/RHDHBUGS-2770
Solution description:
Moved the
CustomDrawercomponent frompackages/apptoplugins/lightspeed/devto resolve workspace accessibility issues during development. This ensures the component is directly available to the dev plugin without relying on the app workspace package✔️ Checklist