Van Tran
Van Tran
Wow, quick fix. Thanks @aduh95
All feedback has been resolved. Thank everybody for taking the time to work on my PR. Thank @RaynaldM for your reviews.
Hi @raman-m 1. - **Why Use the Metadata Name?** The linked issue lacks a detailed design; the term "Extensions" is merely a suggestion. In my opinion, "Metadata" carries a much...
@raman-m I found no reason to add support strong types in metadata. It only increases the complexity of the current codebase. IMO, key-value pairs in string provide almost all capabilities...
@Burgyn IMO those kinds of extensions should be implemented by the developers because the formats of the metadata property vary (delimiter-separated values, JSON values, etc) and I want to keep...
@raman-m Yes, I didn't work on it. I will implement those methods soon.
> @vantm Tiny problem in integration tests. @raman-m Yes, it has been fixed, and extension methods are implemented as well. CC: @Burgyn
If we configure `RouteClaimsRequirement` like this: ```json "RouteClaimsRequirement": { "http://schemas.microsoft.com/ws/2008/06/identity/claims/role": "Admin" } ``` The real result looks like: ```json "RouteClaimsRequirement": { "http": { "//schemas.microsoft.com/ws/2008/06/identity/claims/role": "Admin" } } ``` That why...
@NiranjanGodboleMaersk You must add the extension method `DecorateClaimAuthoriser` right after the method `AddOcelot`.
Hi @JnLlnd , I found this [question ](https://stackoverflow.com/questions/730133/invalid-characters-in-xml) on StackOverFlow. It may help you. Thanks, Van