Skip to content

docs: document interceptor registration for non-REST calls #814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 11, 2025

Conversation

MartinBernstorff
Copy link
Contributor

@MartinBernstorff MartinBernstorff commented May 6, 2025

Documents sharp edge re: interceptor registration (#641).

@MartinBernstorff MartinBernstorff changed the title docs: document interceptor registration for non-rest calls docs: document interceptor registration for non-REST calls May 6, 2025
@jkiddo jkiddo requested a review from Copilot May 6, 2025 18:13
@robogary
Copy link

robogary commented May 6, 2025

Formatting check succeeded!

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Documents the interceptor registration process for non-REST calls in the server. Key changes include:

  • Clarifying the interceptor discovery methods with revised numbering.
  • Adding a note on manual interceptor registration and its impact on non-REST operations.

Comment on lines 358 to 362
Interceptors will be discovered in one of two ways:

1) discovered from the Spring application context as existing Beans (can be used in conjunction with `hapi.fhir.custom-bean-packages`) or registered with Spring via other methods

or
1) From the Spring application context as existing Beans (can be used in conjunction with `hapi.fhir.custom-bean-packages`) or registered with Spring via other methods
2) Classes will be instantiated via reflection if no matching Bean is found

Copy link
Preview

Copilot AI May 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section header incorrectly implies there are only two discovery methods, yet manual registration is discussed immediately after. Consider separating the manual registration note into its own clearly labeled section to improve clarity.

Copilot uses AI. Check for mistakes.

@jkiddo jkiddo requested a review from patrick-werner May 7, 2025 11:14
@jkiddo jkiddo merged commit 5ee2e47 into hapifhir:master May 11, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants