The page contains a lot of references to sample code, and includes comments like "Code removed for brevity", but I can't find a link to the actual code. This makes it really hard to grasp the whole picture as the codes is very limited and shows only the exact things talked about.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ChrisKlug @Rick-Anderson
I could add src code projects for this if you want. Most of the code was built using snippets from this repo:
https://github.com/damienbod/AspNetCoreHybridFlowWithApi
Greetings Damien
I found that repo after Googling it, but the problem is that it is not linked anywhere in the page. This makes it really hard to find, and makes the code hard to understand to be honest.
The problem with moving the samples into the repo is keeping them up-to-date. Given that you, @damienbod, are the topic author and keep that repo up-to-date, I recommend cross-linking that repo as an additional resource for the topic. If you ever stopped keeping that repo up-to-date in the future, then I recommend that they physically come into the repo (and drop the additional resources link).
In addition to a title, you can also add some parenthetical info. For example something like ...
* [Authentication samples (damienbod/AspNetCoreHybridFlowWithApi GitHub repository)](https://github.com/damienbod/AspNetCoreHybridFlowWithApi): Code examples in this article are demonstrated in the sample apps.
:point_up: That's just an example. Make it say whatever you think best. It's probably a good idea to label it as an external GH repo somewhere.
I 'll do a PR then. @guardrex What's the best way to link it? A note at the top and a link?
@ChrisKlug Would you find this good, would this help?
Greetings Damien
I would say that a link at the top would be awesome! It would make it nice and easy to clone the repo before reading the code.
Cheers,
Chris
We generally only link samples that are part of the repo at the top. Since I don't think we should host the samples in this case, I recommend placing the cross-link into the Additional resources section at the bottom.
This is a somewhat arbitrary opinion tho. We'll ask Rick to review+approve the PR. You can put the link at the top and see if he thinks it will be ok. Something like ...
[View or download sample code (damienbod/AspNetCoreHybridFlowWithApi GitHub repository)](https://github.com/damienbod/AspNetCoreHybridFlowWithApi)
... immediately under the author byline.