Correct Grouping of related Entities

[stsiushkevich]

Hello! I have a typical situation when there are some set of related entities(slices). For example we have Employee entity, and related EmployeeGroup and EmployeeRoleGroup entities and appropriate TS Types. For all of them there are according data lists, that displayed on the page and fetching data from the server. Should I leave these slices like separated at the same @entities layer, or unite them to a single slice Employee?

[illright]

I would recommend keeping the slices flat as long as possible, and only when it starts to overflow with slices, you can start grouping them. Note that when you group slices into a folder, they don't become one slice. In the case below:

• entities/
  • Employee/
    • Person/
    • Group/
    • RoleGroup/
  • Identification/

The slices are Employee/Person, Employee/Group, and Employee/RoleGroup, and these slices are bound by the same rules as Identification, no code sharing is permitted between Employee/* slices.

[dante01yoon]

I would recommend keeping the slices flat as long as possible, and only when it starts to overflow with slices, you can start grouping them. Note that when you group slices into a folder, they don't become one slice. In the case below:

• entities/

  • Employee/

    • Person/
    • Group/
    • RoleGroup/

  • Identification/

The slices are Employee/Person, Employee/Group, and Employee/RoleGroup, and these slices are bound by the same rules as Identification, no code sharing is permitted between Employee/* slices.

Hi @illright,
isn't it Employee is slice and each nested Person, Group, RoleGoup is segments?
Also, isn't it available sharing code between segment is possible?

[illright]

Hi @dante01yoon, no, in this case, Employee is a slice group. Slice groups are just regular folders with slices. Slices in the same group are bound by the same rules as other slices — the slice Employee/Person cannot share any code with Employee/Group. Notice that when I write the names of these slices, I include the group in the name.

[dante01yoon]

@illright Hey thanks for details. How deeply can I manage slice directory ?
in this case, you suggested Employee/Person as a slice group, can I make it deep nested like Employee/Someting/Person or more than?

[illright]

You can go as deep as you want, but I'd advise to take caution here. Usually, too deep of a grouping is a sign of overslicing

[dante01yoon]

Got it, thanks !