manyminds / api2go

80%

master: 80%

LAST BUILD ON BRANCH nested-item-get-route

branch: nested-item-get-route

CHANGE BRANCH

x

Reset

• nested-item-get-route
• 0.3
• 0.4
• 0.5
• 0.6
• 1.0-RC1
• 1.0-RC2
• 1.0-RC3
• 1.0-RC4
• 274-nested-resource-routes
• HEAD
• apiReturnCodes
• asynchronous-processing
• attributes-optional
• badge-updates
• bugfix-unmarshal-embedded-struct
• bugfix-unmarshaler-interface
• clean_string_fix
• cleanup
• context-package
• coverage
• custom-meta-in-relation
• data-null-response
• default_response
• dependabot/go_modules/golang.org/x/crypto-0.31.0
• dependabot/go_modules/golang.org/x/net-0.38.0
• different-types-to-many-relationship
• documentation-middleware-context
• documentation_upgrade
• drop-go-17
• dynamic_baseurl_handling
• echo-adapter
• example-create-with-relationships
• export-errors
• fix-crud-documentation
• fix-double-forward-slash
• fix-getFieldByTagName
• fix-tests
• foreignIDintegration
• format-police-coverage
• framework-routing
• github-actions
• go-17-travis
• gofmt_simplify
• handleUpdate-empty-information
• hotfix
• int64ids
• internal-data-structs
• ir-rn-upgrade-deps
• issue-154
• issue_stats
• it-use-gomod-for-gha-versioning
• jsonapi-ignore-tag
• lint-only-on-some-versions
• marshal-composition
• marshal-includes-recursively
• master
• migration_guide
• nullValueUnmarshal
• patch-id-conflict-error
• private_fields_warning
• readme-httperror
• readme_fixes
• readme_upgrade
• register-multple-api-versions
• remove-issuestats
• remove-tip
• remove_migration
• report_card
• router_replacement
• security/golang.org-x-net
• sharpner-lint-fix
• sharpner-patch-1
• sparse-fieldsets
• unmarshal-slice-fix
• unmarshaling-array-attributes
• update-dependencies
• update-travis
• v0
• v1

Build # 30127016656

Build Type

Pull #5

Committed by josegonzalez

Commit Message

feat: add nested item GET route for composite resources

Composite nested resources answered POST on the collection and DELETE and PATCH on the item, but had no GET at the nested item path, so item reads fell back to the flat top-level route. This registers GET on the nested item path for resources that expose a child segment, injecting the parent id like the other nested handlers. To-one nested resources are excluded because their item path is the parent relation route, which already answers GET.

Pull Request Pull Request #5:

Coverage Stats

1467 of 1828 relevant lines covered (80.25%)

33.34 hits per line