René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Use `records` for joined resources","articleBody":"## This issue is a (choose one):\r\n\r\n- [ ] Problem/bug report.\r\n- [x] Feature request.\r\n- [ ] Request for support. **Note: Please try to avoid submitting issues for support requests. Use [Gitter](https://gitter.im/cerebris/jsonapi-resources) instead.** \r\n\r\n## Checklist before submitting:\r\n\r\n- [ ] I've searched for an existing issue.\r\n- [ ] I've asked my question on [Gitter](https://gitter.im/cerebris/jsonapi-resources) and have not received a satisfactory answer.\r\n- [ ] I've included a complete [bug report template](https://github.com/cerebris/jsonapi-resources/blob/master/lib/bug_report_templates/rails_5_master.rb). This step helps us and allows us to see the bug without trying to reproduce the problem from your description. It helps you because you will frequently detect if it's a problem specific to your project.\r\n- [X] The feature I'm asking for is compliant with the [JSON:API](http://jsonapi.org/) spec.\r\n\r\n## Description\r\n\r\n**Current:**\r\n\r\nIn version 0.9 and earlier JR relied on the Rails eager loading using the ActiveRecord `includes`. In a typical Rails app this feature works great, but we ran into a lot of edge cases and performance compromises when auto generating the queries JR needs for complex requests - especially ones with complex includes. In addition the complexity grew with caching.\r\n\r\nWith this approach we recommended that related resources be controlled using `relation_name` on the relationship. This relation was used in the includes and provides a way to control the related resources.\r\n\r\nWith version 0.10 the approach was changed and we no longer use rails eager loading. The `relation_name` on the relationship can still be used for relationship filtering.\r\n\r\nThere is also the option of using the `apply_join` callable on the relationship.\r\n\r\nBoth of the above options however require explicitly wiring up the appropriate code on each relationship.\r\n\r\n**Proposed change:**\r\n\r\nWhen joining related records in `ActiveRelationResource.apply_join` we have to opportunity to use ActiveRecord's `merge` method to apply the related resource's `records` logic. The implication of this is all accesses to a Resource will use the same `records` applied logic whether coming to the resource as the primary resource in a request, as an included resource, or through the `related` link of the parent resource.\r\n\r\nI believe this one change should drastically simplify resource authentication and opens up some further opportunities to further simplify most resources.\r\n","author":{"url":"https://github.com/lgebhardt","@type":"Person","name":"lgebhardt"},"datePublished":"2020-02-10T13:10:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1308/jsonapi-resources/issues/1308"}