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
{{ message }}
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
Adding roasters domain is a bit of a long term goal. Likely will be implemented as a many-to-many relationship with shops. IDK if I should add to map. Many coffeeshops are roasters already and making a distinction would be confusing.
My idea for the roaster field in the shop details page looks like one of the following:
# null case
roaster: unknown
# they roast their own beans
roaster: self
# roaster partner
roaster: <a href="/roaster/{roaster.id}">{roaster.name}</a>
I also have to think about the case where the shop has multiple roaster partners. Should shop's roaster be roasters?
Also, what if the shop roasts their own, but the roaster name differs from the shop name?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Adding roasters domain is a bit of a long term goal. Likely will be implemented as a many-to-many relationship with shops. IDK if I should add to map. Many coffeeshops are roasters already and making a distinction would be confusing.
My idea for the roaster field in the shop details page looks like one of the following:
I also have to think about the case where the shop has multiple roaster partners. Should shop's
roaster
beroasters
?Also, what if the shop roasts their own, but the roaster name differs from the shop name?
The text was updated successfully, but these errors were encountered: