Umbrella: pending work for v4

[bart-degreed]

This tracking issue lists work to consider before release of JADNC v4.

v4.0.0-alpha5 (released)

• Code quality Code cleanup #691
• Bugfix Bug: custom serializer settings are ignored #687
• Bugfix Breaking change: null data returned when resource not found #631
• Memory leak EFCore based Memory Leak #450
• Params in paging links Include sort and include params in pagination links #276
• SourceLink Restore SourceLink support #692
• Fail on Patch ID mismatch Possible mismatch between ID in URL and Patch body #702
• Hooks Feature request: improved hook support #623 -> Disabled resource hooks by default, as they are still experimental #717
• Review logging Review logging #689
• Encoding bugfix Filtering on special chars sends back an un-escaped special character in the links urls #408
• Error handling Invalid Patch request body format required (most likely user error) #655
• json:api spec compliance Response when updating attributes of resource not conform spec #577
• Parallel tests Cannot run tests in parallel because TypeLocator is using a static cache shared between tests #485
• Auto-inclusion How to include nested EF entities in include #652
• Default attribute capabilities Default attribute capabilities #707
• Bugfix Bug: relations are lost when using sparse fieldset combined with include #708
• Bugfix Bug: validations do not run on POST with invalid content type header #725
• Bugfix Create (POST) does not return entity including changed values from trigger #724
• Context injection Feature request: support resources with injected DbContext #657
• Validation PATCH with ValidateModelState enabled and [Required] attribute #472

v4.0.0-beta1

• Fixed: missing property setter in options Fixed: missing property setter in options #742
• Fixed: GetDefaultSortOrder is never called Question: GetDefaultSortOrder not firing #736
• Fix in error handler Fixed: do not intercept exceptions thrown from non-json:api requests #749
• Fixes sorting on multiple fields Bug: sorting on multiple fields does not work #745
• Fixed: error when setting non-string default filter Fixed: error setting default sort for non-string properties #754
• Filter validation fix Bug: Filter passes query validation, but the filter is not applied #659
• Cleanup example projects Projects cleanup #744
• Improved error message in serializer Improve Error Message For Invalid Objects Passed To Serializer #270
• Documentation updates Documentation updates for v4 #741
• Cleanup UseJsonApi Cleanup implementation of UseJsonApi #733
• Review all TODOs in code and assess severity Resolved most ToDo's in code #759
• Delete response causes exception in Kestrel Response content with 204 response code #760
• Namespace not honored when using relative links Namespace not honored when RelativeLinks=true #763
• Composable filters and deeply nested queries Composable filters and deeply nested queries #792
  Fixes Filter expression translation #788, Hard-coded convention #787, Ultimate default sort #764, Breaking: change filters to compose as OR instead of AND #761, Simplify/optimize filter query string parsing #758, Unexpected behavior on negative page number #757, Feature: Paging and filtering on nested endpoints #751, Feature: sparse fieldsets on nested endpoints #748, Feature: sort on nested endpoints #747, Custom query filter using repository does not work #738, support filtering by (non-)existing relationships #551, Escaped Commas cannot be used in a filter string #444, Restrict maximum page size per resource #217, Filter OR operator and complex predicates #183, Custom Queries w Validation #176
• Review public API surface (namespaces and publicly exposed types) Review public API surface #734
• More documentation updates Read through docs and update (focus on hooks + differences to v3) #567
• Fix: Routing does not respect custom resource name PluralizedTypeName option when adding resource doesn't work for routing #786
• ... and a few more

[bart-degreed]

@maurei as requested, my wish list. Feel free to edit.

[bebizzle]

@maurei - quick question, when are you guys planning to release the next alpha version? My team and I have noticed some divergence between master and what is in Nuget.

[rachael-ross]

Any idea on release timing?

[bart-degreed]

Closing this, because as a project contributor I can now use (open/close/reassign/label) issues directly.