Add Duende.Bff.Blazor #200
Closed
Conversation
This file contains 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
josephdecock
force-pushed
the
blazor-reworked
branch
from
1b7dbac
to
66b3997
Compare
josephdecock
force-pushed
the
blazor-reworked
branch
from
66b3997
to
68ba711
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the core PR adding Blazor server and client nuget packages. Reworked samples using these packages will be merged separately, to keep this PR manageable.
The main idea is to combine the two approaches we've used historically: when using wasm, we need a BFF; when using blazor server, we need a server side (non http context based) token store. We use the existing bff server side session, and wire that into everything so that we can manage a consistent set of tokens regardless of the render context.
We also have helpers to create http clients that are appropriate for both blazor server and wasm. On blazor server, we retrieve the access token and use it. On wasm, we proxy the request through the bff. From the point of view of the component or service running in the blazor application, you just use an http client.