[dblock]

What this fixes

With the AMS JSON adapter, collections already have a root envelope. This PR fixes two ignored root overrides; it does not introduce collection wrapping or change its defaults.

1. An explicit namespace root was ignored: the collection used the namespace name instead of the configured root.
2. A root passed to render was not forwarded to AMS: the response kept the route or inferred root instead of the requested override.

For example:

namespace :users, root: 'members' do
  get('/')    { User.all }
  get('/:id') { User.find(params[:id]) }
end

Response with the JSON adapter	Before	After
Collection in the namespace above	{"users": [...]}	{"members": [...]}
Single user in that namespace	{"user": {...}}	Unchanged
Collection in namespace users without an explicit root	{"users": [...]}	Unchanged

Explicit collection roots follow inner namespace > outer namespace, route > namespace, and render > route precedence. Empty collections retain an explicit root too.

What stays unchanged

Namespace roots remain collection-only: the earlier draft unintentionally renamed single-object responses, and that regression is removed. Existing route-level roots continue to work. The attributes adapter still returns bare arrays; root:false does not remove the JSON adapter envelope; JSON:API retains its standard data structure. Grape format :json still does not select the AMS adapter.

The implementation reads only namespace root options for collections rather than broadly changing namespace-option handling. Documentation explains adapter selection and precedence, and nine request-level cases cover collection behavior and preservation of single-object roots.

Validation

All 84 examples and RuboCop pass locally with Grape 4 on Ruby 4.0. No dependency changes, new source exclusions, or increased lint limits.

Hosted CI passes the compatibility matrix and lint. Danger also passes.

Closes #81.

Created by Copilot, an AI, on behalf of @dblock.

[github-actions]

Danger Report

No issues found.

View run

[samsonjs]

This changes behaviour of object responses in addition to collections. Previously a namespace root: was ignored and the response key was derived from the returned object's class. This isn't a feature that I use and I'm honestly unsure if this is intentional, but it seems at least worth documenting and adding to the changelog.

[dblock]

Fixed in 81bac6b: namespace-root lookup is now collection-only, preserving the existing single-object response key. Added regression coverage and clarified the README/changelog.

Posted by Copilot, an AI, on behalf of @dblock.

[dblock]

Keeping this fix collection-only preserves compatibility. For example, with namespace :users, root: "members", a collection returns {"members": [...]}, while a single user continues to return {"user": {...}} rather than unexpectedly becoming {"members": {...}}. Individual routes can still choose an explicit root.

Applying namespace roots uniformly to collections and single objects could be a reasonable long-term API, but that would be a deliberate breaking change for a major release, not part of this collection-root fix.

Posted by Copilot, an AI, on behalf of @dblock.

[dblock]

Major version bump and a consistent root handling in #111, your call @samsonjs !