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 Jan 19, 2022. It is now read-only.
At the moment, the values for repo and user_model are worked out by the Openmaize.Utils module, and they are evaluated to be MyApp.Repo and MyApp.User. With Phoenix 1.3, MyApp.User should be MyApp.Accounts.User, but this is Phoenix-specific, and one of the goals of Openmaize is that it is not tied down to any particular framework.
The current plan is to add these values to the config. The branches phx_1.3 and develop show examples of this, the difference between them being that phx_1.3 allows these values to be overridden, whereas in the develop branch, the values are fixed.
My preference is for the version in the develop branch. However, if someone can provide a strong argument for allowing these values to be overridden, I will accept that.
The text was updated successfully, but these errors were encountered:
At the moment, the values for repo and user_model are worked out by the Openmaize.Utils module, and they are evaluated to be MyApp.Repo and MyApp.User. With Phoenix 1.3, MyApp.User should be MyApp.Accounts.User, but this is Phoenix-specific, and one of the goals of Openmaize is that it is not tied down to any particular framework.
The current plan is to add these values to the config. The branches
phx_1.3
anddevelop
show examples of this, the difference between them being thatphx_1.3
allows these values to be overridden, whereas in thedevelop
branch, the values are fixed.My preference is for the version in the
develop
branch. However, if someone can provide a strong argument for allowing these values to be overridden, I will accept that.The text was updated successfully, but these errors were encountered: