You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am new to commanded and I come from the rails.
I found there are two big contexts or aggregates. one is called blog (lib/conduit/blog), another is called accounts(lib/conduit/accounts).
I am not sure if we need to keep some kind of consistency for these two naming ?
which is better or how to choose , as in rails, we normally have convention about naming.
The text was updated successfully, but these errors were encountered:
I'm not sure whether there are any rules around whether contexts need to be consistently named in either plural or singular form. For example the Phoenix documentation on Contexts defines three contexts named as Catalog, ShoppingCart, and Orders.
Naming things is hard. If you're stuck when trying to come up with a context name when the grouped functionality in your system isn't yet clear, you can simply use the plural form of the resource you're creating. For example, a Products context for managing products. As you grow your application and the parts of your system become clear, you can simply rename the context to a more refined name at a later time.
You are free to enforce any convention you like, or none at all.
Hi, I am new to commanded and I come from the rails.
I found there are two big contexts or aggregates. one is called blog (lib/conduit/blog), another is called accounts(lib/conduit/accounts).
I am not sure if we need to keep some kind of consistency for these two naming ?
which is better or how to choose , as in rails, we normally have convention about naming.
The text was updated successfully, but these errors were encountered: