agentsclimarketplace

Create doctrine repository

Skill jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/CQRS/skills/create-doctrine-repository

Create the repository in the Adapter layer. This is the ONLY class that touches the database — all handlers delegate to it. Covers multistore patterns with ShopConstraint when the entity requires it. Trigger: "create repository for {Domain}".From its SKILL.md

Install
npx -y skills add jeffsenso/prestashop-skills --skill create-doctrine-repository

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 531 tokens by cl100k_base, as published. Nobody here has run it

create-doctrine-repository

See CQRS/CONTEXT.md for conventions (stateless, no Context dependency, multistore tier model, typed exceptions).

1. Choose the base class

Create src/Adapter/{Domain}/{Domain}Repository.php. Choose the base class based on the multistore tier table in CONTEXT.md.

2. Core methods

Implement these methods (adapt naming to your domain):

  • get{Domain}({Domain}Id $id): {LegacyObjectModel} — loads the ObjectModel, throws {Domain}NotFoundException if not found
  • create(...): {Domain}Id — calls ObjectModel save() or add(), wraps in try/catch, returns new ID
  • update(...) — calls ObjectModel save() or update()
  • delete({Domain}Id $id) — deletes the entity, respects multistore if applicable

Reference: src/Adapter/Tax/CommandHandler/ uses a simple repository pattern, src/Adapter/Carrier/CommandHandler/ uses AbstractMultiShopObjectModelRepository

3. Multistore pattern (when using AbstractMultiShopObjectModelRepository)

  • Receive ShopConstraint as a method parameter — never read it from Context
  • Call $shopIds = $this->getShopIdsByConstraint($shopConstraint) at the start of every write
  • Iterate $shopIds and apply the write for each shop context
  • Modes: ShopConstraint::allShops(), ShopConstraint::shop($shopId), ShopConstraint::shopGroup($groupId)
  • Single-shop installs still go through this path (returns array with one ID)

4. Sub-resource methods (if applicable)

For entities with has-many sub-resources, two strategies:

Atomic replace (simpler)

  • set{SubResource}s({Domain}Id, array $items) — delete all existing rows, insert new set
  • Wrap in transaction — partial replace corrupts data

Incremental update (cleaner)

  • Compare existing rows with new collection, apply only changes
  • Preferred when sub-resources have their own identity

Rules

Conventions (stateless, no Context, typed exceptions) are in CQRS/CONTEXT.md. Skill-specific reminders:

  • Never use Db::getInstance() — use Doctrine DBAL or ObjectModel methods
  • Never hard-code Context::getContext()->shop->id — receive shop as parameter

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,059. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.