Justin Yoo

@toriverly Thanks for the issue! I'll take a look.

As this introduce breaking change to `IOpenApiExample`, it should be re-labelled to `v2.0.0`

There are two places you need to inject the `IOpenApiConfigurationOptions`: https://github.com/Azure/azure-functions-openapi-extension/blob/4e81588f399f642236e354f00f64de99dccb859a/src/Microsoft.Azure.Functions.Worker.Extensions.OpenApi/OpenApiHttpTriggerContext.cs#L173-L178 https://github.com/Azure/azure-functions-openapi-extension/blob/4e81588f399f642236e354f00f64de99dccb859a/src/Microsoft.Azure.WebJobs.Extensions.OpenApi/OpenApiHttpTriggerContext.cs#L172-L177 The `IOpenApiConfigurationOptions` instance already exists as a private field in there. However, there are two other places as...

@KeenFann Thanks for the issue! If you change the property name to something else, say `MyParameters` and give it a decorator of `[JsonProperty("parameters")]`, does that still throw an exception?

@manekinekko I have the exact same issue, using SWA CLI v1.0.3. Here are my log file: ``` ❯ swa deploy -d $swa_key --env default --verbose=silly Welcome to Azure Static Web...

@ihordyrman Thanks for the issue. In your specific case, you might like to use the route template. ```csharp [Function("HttpTrigger")] [OpenApixxxx(...)] [OpenApiParameter(name: "version", Type = typeof(string), In = ParameterLocation.Path ...)] public...

@jvmlet Thanks for the issue! Yes, we're aware of that, but it's de-priotised over other issues. Let's keep this open for further discussion.

Related: #343

As the PR, #489, has been merged, you can generate the OpenAPI doc on-the-fly, within the GitHub Actions workflow.

Thanks everyone for the long wait! I've got a couple of items to be merged into v1.4.0, which are on the review. Please wait for a little bit longer!