SeaQL / SeaQL/seaql.github.io

Reason why `ActiveModelBehavior` only works with methods defined on `ActiveModelTrait`

Open
#171 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
HTML
Stars
24
Forks
68
No merged PRs in 30d

Description

  • Entity accepts A: ActiveModelTrait<Entity = Self>, but A is not necessarily Entity::ActiveModel.
  • DeleteOne<E> does not carry a generic parameter for ActiveModel, making it incompatible with behavior hooks.
  • Insert::exec does not return the model, so after_save cannot be triggered.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the ActiveModelBehavior, ActiveModelTrait, Entity, DeleteOne, and Insert::exec entry points named in the issue. Determine the intended generic and return-value behavior for the listed hooks; done means the incompatibilities are resolved and the relevant behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend-api-design
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.