forked from json-api-dotnet/JsonApiDotNetCore
-
Notifications
You must be signed in to change notification settings - Fork 0
Merge to latest version #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat(DocumentBuilder): allow for output attribute filtering
feat(csproj): add SourceLink
fix(AttrAttribute): unexpected scenarios cause breaking change
specify symbols server for develop
v2.3.4 Introduce ResourceDefinition
…-logging chore(appsettings): supress middleware logging
test/#318: empty collection returned for PATCH requests
fix(operations): interface hierarchy
develop → master: operations
this is because we made the ContextGraph a static instance...if C# ever supports interfaced statics, we could swap the IContextGraph source when the test assembly starts executing
…cution fix(#337): run tests serially
Add new MappingResourceService that can be used to separate and map between Entity Framework objects and JSON-API data transfer objects Added new example project, ResourceEntitySeparationExample, showing how to configure an entity/resource split and corresponding tests.
…ying the internal name instead of only inferring it from the dto variable name, as that may not match the entity relationship name
…-many entity required by ef core
fix(ServiceCollectionExtensions): correct service scoping
…it untyped for now to match how automapper works
…dent-has-one fix(Deserializer): deserialize indpendent hasone pointers
feat(#112): Entity and Resource separation
test(acceptance): Can_Create_And_Set_HasOne_Relationships_From_Indepe…
Entity Resource Separation (2.4.0-beta3)
Should consider creating a new API on the graph that is more intuitive and doesn't require both steps.
Fix/#354: Null reference exception when fetching relationships with compound name
Fix/#340: Operations issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #{ISSUE_NUMBER}
BUG FIX
FEATURE