Skip to content

Commit f3e90e6

Browse files
committed
docs(feedback): clarify legacy vs new frontend setup steps
1 parent 40610c7 commit f3e90e6

File tree

1 file changed

+9
-4
lines changed
  • workspaces/feedback/plugins/feedback

1 file changed

+9
-4
lines changed

workspaces/feedback/plugins/feedback/README.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,14 +37,19 @@ It is dedicated to simplifying the process of gathering and managing user feedba
3737
- Make sure that [feedback-backend-plugin](../feedback-backend) is configured prior to this.
3838

3939
### Plugin Setup
40-
## New Frontend / Hybrid Migration Notice
40+
41+
## New Frontend / Hybrid Migration Notice
4142

4243
The Feedback plugin currently has limited support for the new
4344
Backstage frontend and hybrid migration setups.
4445

45-
Some setup steps in this documentation apply only to the legacy
46-
frontend and may not work as expected with the new frontend.
47-
---
46+
The following steps are **legacy frontend only**:
47+
48+
- Adding routes in `App.tsx` using `FlatRoutes`
49+
- Registering components directly in `AppRouter`
50+
51+
## The backend configuration and catalog annotations remain the same for both legacy and new frontend setups.
52+
4853
1. Install the plugin in your environment
4954

5055
```bash

0 commit comments

Comments
 (0)