Let Us Know Your Configuration Needs

[webJose]

This package is the early stages. It works perfectly, but would like to understand if there is out there a popular need that we are not currently covering.

Just drop a response in this issue telling us which properties you configure the most in Ocelot that we do not currently cover and we'll expedite a new package version with the most popular choices.

Thank you for your time and collaboration! It is much appreciated.

[jjenkinsmram]

RouteClaimsRequirement! As in:

"RouteClaimsRequirement": {
            "Role": "READ"
          }

I created my own class that inherits from OcelotRoute, but it doesn't seem to be picked up by your code. Exactly what has to be done to have a custom OcelotRoute? I tried declaring my OcelotRoutes with my custom OcelotRoute, but then the extension method doesn't work.
Would it be better if OcelotRoute was a partial? That seems easier to allow for implementation of other properties.

[webJose]

Hello. Thank you for your interest. I am currently tied up at work. I will have a look at this tomorrow or on Saturday.

[jjenkinsmram]

Has anyone tried to use an ocelot aggregator with your library (which, btw, is very useful)? I worked through the ocelot documentation and it just didn't work.

[webJose]

Apologies for the tardiness. My attention has deviated to single-spa these couple of months. No, not to my knowledge.