Releases: json-api-dotnet/JsonApiDotNetCore
Releases · json-api-dotnet/JsonApiDotNetCore
v2.4.0
No functional changes after v2.4.0-beta4. Below is a summary of all the changes released.
#360 via #361: Added nin
(not-in) filter. Thanks @milosloub!
#354 via #355: Fix bug introduced in v2.4.0-beta3
#112 via #344, #352: Entity and Resource separation. Thanks @roblankey !!
#339 via #345: fix service scope registrations (Cannot consume scoped service IGenericProcessorFactory from singleton IOperationProcessorResolver)
#349 via #348: fix(Deserializer): deserialize independent HasOne pointers
#322 via #333 fix(relationship pointers): Can't create entity with two HasOne attributes pointing to same entity
#335 / #336 various operations fixes
v2.4.0-beta4
v2.4.0-beta3
#112 via #344, #352: Entity and Resource separation. Thanks @roblankey !!
v2.4.0-beta2
v2.4.0-beta1
v2.3.4
- #321 via #325: Add support for SourceLink. You can now debug into JADNC source code from Visual Studio and VS Code.
- #297 via #324: Runtime attribute filtering. Although this is considered a non-breaking change, there is a known issue you may run into. Because of the differing semantics between some IoC containers, you may encounter issues where
ResourceDefinition<T>
cannot be resolved. This is because we do an optional lookup on theIServiceProvider
interface. Any implementations ofIServiceProvider.GetService(Type)
that throw an exception for services not existing on the container could result in a failure. You should make sure that any custom implementations do not throw. This is a non-issue for anyone using Microsoft.Extensions.DependencyInjection.