This is a roadmap for getting to version 1.0.

• [Authorize relationship actions with custom policy methods #40] Allow authorization of relationship operations separately
• [Add tests for every scenario of the relationship operations #47] Add exhaustive tests for the new relationship operation policies
• [Default pundit authorizer keyword args #95] The API of DefaultPunditAuthorizer methods could be changed to use keyword arguments
  • Currently the API change is backwards-incompatible in a way that could be very confusing,
    namely as replace_to_one_relationship has the same amount of parameters but are very
    different than what there was before
  • Keyword arguments are supported ever since Ruby 2.0 so we can use them
• [Handling relationship policy checking in replace_fields #51] Look into the API of DefaultPunditAuthorizer#replace_fields and figure out if it could be implemented similarly to Authorize relationship actions with custom policy methods #40 did
  • The replace operation could even call the new replace/remove relationship authorization methods
  • If this wouldn't be done, we might need to bump to v2.0.0 after implementing as it would be a major breaking change in the API... so better look into it sooner than later
• [Authorize related records on #create_resource #60] Authorize relationships when creating a new resource
• [PR / Help wanted] Document a design pattern for specifying relationship operations logic only once
  • API proposal for authorizing relationships #30 (comment) is a good first start
  • EDIT on 2019-01-22: After a lack of contributions, this was postponed to a future time.
• [Make compatible with jsonapi-resources 0.9 #52] Fix compatibility with v0.9.0 of jsonapi-resources Not compatible with v0.9.0 of jsonapi-resources #36
• [Authorize replacing of a polymorphic has-one relationship #75] Figure out what to do with the replace_polymorphic_to_one_relationship
  • This case that was found in Make compatible with jsonapi-resources 0.9 #52 (comment)
• [add rails 5.0 5.1 5.2 to ci builds #98] Test with Ruby 2.3
• [add rails 5.0 5.1 5.2 to ci builds #98] Test with rails 4.2, 5.0, 5.1 and 5.2
• Release an alpha of 1.0.0 and gather feedback
• Start using the latest release internally at Venuu
• Release a beta of 1.0.0 and gather feedback

...is there anything I've missed?

This roadmap is intended to be a live documentation that can be changed later as need be.