Skip to content

"Unused request header descriptions" yielded if not directly referenced #248

@nickvergessen

Description

@nickvergessen

In Talk we have a middleware which e.g. takes care of federated authentication. We should therefore document the x-nextcloud-federation header on all controller methods that support federation.
There is 1 inconvenience with this and 1 error:

  1. It's duplicating the existing #[FederationSupported] attribute we have and if that one extends RequestHeader it is not reflected in the docs.
  2. When adding it manually the openapi-extractor is complaining, even though the header is read in the depth of the middleware:
Error: Avatar#getAvatar: Unused request header descriptions: x-nextcloud-federation
Error: Avatar#getAvatarDark: Unused request header descriptions: x-nextcloud-federation
Error: Avatar#getUserProxyAvatarWithoutRoom: Unused request header descriptions: x-nextcloud-federation
Error: Avatar#getUserProxyAvatarDarkWithoutRoom: Unused request header descriptions: x-nextcloud-federation
Error: Avatar#getUserProxyAvatar: Unused request header descriptions: x-nextcloud-federation
Error: Avatar#getUserProxyAvatarDark: Unused request header descriptions: x-nextcloud-federation

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

Status

☑️ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions