Expected Behaviour
We used this linter plugin with a on-premise installation of Zally. Furthermore, we forked the Zalando API guidelines and modified the Zally rules to be consistent with your ohn API guidelines.
We would love to configure this plugin to point to your self-hosted API guidelines and name it accordingly to not confuse our users if they should follow our guidelines or the Zalando ones.
It would be nice the have the following occurances to be configurable.
Actual Behaviour
The name and url of the link in the header is hard coded, see here

Should be the following lines in code:
|
to="https://sunrise.zalando.net/docs/default/Component/api/" |
|
Zalando's RESTful API and Event Guidelines |
The header of the list of rules is hardcoded:

See code:
|
<Typography variant="h5">Zalando's API Rules</Typography> |
Steps to Reproduce the Problem
- Open the overview and see the header
- Open the rules and see its header
Expected Behaviour
We used this linter plugin with a on-premise installation of Zally. Furthermore, we forked the Zalando API guidelines and modified the Zally rules to be consistent with your ohn API guidelines.
We would love to configure this plugin to point to your self-hosted API guidelines and name it accordingly to not confuse our users if they should follow our guidelines or the Zalando ones.
It would be nice the have the following occurances to be configurable.
Actual Behaviour
The name and url of the link in the header is hard coded, see here

Should be the following lines in code:
backstage-plugin-api-linter/src/components/Header/Header.tsx
Line 52 in b2e9d17
backstage-plugin-api-linter/src/components/Header/Header.tsx
Line 61 in b2e9d17
The header of the list of rules is hardcoded:

See code:
backstage-plugin-api-linter/src/components/Rules/Rules.tsx
Line 44 in b2e9d17
Steps to Reproduce the Problem