v2.5.1

#343 via #373 reload relationships from database if included during POST
#362 via #374 improve error message for null HttpContext
#313 via #375 do not return 409 for generic InvalidCastException

v2.5.0

Thanks @rtablada !
#367 via #369 Make Error.Source an object instead of string
#370 Add GetPublicAttributeName to Context Graph
#371 Set Error.Source when constructing validation errors

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

#354 via #355: Fix bug introduced in v2.4.0-beta3

v2.4.0-beta3

#112 via #344, #352: Entity and Resource separation. Thanks @roblankey !!

v2.4.0-beta2

#339 via #345: fix service scope registrations (Cannot consume scoped service IGenericProcessorFactory from singleton IOperationProcessorResolver)
#349 via #348: fix(Deserializer): deserialize independent HasOne pointers

v2.4.0-beta1

#322 via #333 fix(relationship pointers): Can't create entity with two HasOne attributes pointing to same entity
#335 / #336 various operations fixes

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 the IServiceProvider interface. Any implementations of IServiceProvider.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.

v2.3.3

#252 via #316 Check ModelState.IsValid if configured. Thanks @sigent!

v2.3.2

#307 via #308: Fixing issue where total-records was 0 on POST and PATCH calls. Thanks @nwise!
#310: fix(IResourceService): inheritance hierarchy creates problems with Autofac
#312 via #314: Deserializer not linking included relationships