Links and auto links behaviours impose out-of-spec limitations.

[Slotos]

According to spec, links object presence is optional in top level and resource objects.

However, this library imposes the following out-of-spec limitations:

• if top level links object is generated (remove_links: false), resource level links object presence is effectively enforced
• if resource level links object is controlled manually (remove_links: true), top level links object is omitted
• when rendering singular resources, top level links object is omitted

The first two limitations make it impossible to implement, for example, a paged list view for identifiable but not individually addressable resources.

[grzuy]

Agree.

We're also struggling with this limitation.