Skip to content

no obvious negation for slices and modules. #1500

@xenoterracide

Description

@xenoterracide

So, I've been using a design that is essentially isolated slices except for a shared "commons" which contains things like ids, Country, Address, etc, which need to be available for more than one aggregate. Problem is neither slices no modules have a way to essentially say "these packages in domain.model" are not allowed to depend on each other except via "domain.model.comons". Now there is a similar method to what I just said, but it still results in a dependency cycle as it's not an exclusion of domain.model.commons

domain.model.user
must not depend on
domain.model.account
or vice versa
both may depend on
domain.model.commons

as of right now commons is my only exception... my other dependencies are enforced via layers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions