-
### Steps to reproduce
```
dotnet ef migrations add InitialCreate --context MyContext --output-dir ./src/services/Data/Migrations --project ./src/services/Core --startup-project ./src/services/Api…
-
### Steps to reproduce
```
dotnet ef migrations add InitialCreate --context MyContext --output-dir ./src/services/Data/Migrations --project ./src/services/Core --startup-project ./src/services/Api…
-
It should not be mandatory to include a (record) field that is `option`al. If an optional field is missing, it should just be treated as `None` imo.
-
As requested by @cmeeren: https://github.com/Tarmil/FSharp.SystemTextJson/issues/24#issuecomment-576616674
It is sometimes necessary to distinguish between a `null` field and the absence of a field…
-
I create a new AWS Lambda .NET Core 3.1 project, then run it using AWS Lambda Test Tools, then I get this page as expected:
![image](https://user-images.githubusercontent.com/4753901/78628801-a9926…
-
...So we can use all the recent changes 😄
--------
In particular I need to depend on the code after the merge of this one: https://github.com/Tarmil/FSharp.SystemTextJson/pull/36
-
Swagger api for an endpoint that accepts an enum query is generated as in values.
I'm with Swashbuckle.AspNetCore.SwaggerGen 5.0.0 and netcoreapp2.2
![image](https://user-images.githubuserconten…
-
Is there a way to prevent System.Text.Json from inserting `null`s at every opportunity?
It seems like whenever a value is missing in the incoming json (either the field is missing, or explicititly…
-
Swashbuckle does not respect newtonsoft serializer setting on .net core 3.1 because of the following line:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/6fd662b7e1f1a9920dcd5a0f5d7…
-
Since 5.0.0-rc5 (rc4 is the latest version with a different behavior) inherited properties are not generated in the model any more:
```
public interface IX
{
string ASD { get; se…
ghost updated
4 years ago