In reality it's rarely possible to completely isolate concerns (groups of schemas) under separate contexts. And then you'll have to alias models (schemas) awkwardly different, and it becomes impossible to tell what is aliased by the name only. What I found way clearer is traditional approach App.Model.User and App.Context.Accounts under model and context dirs respectively.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In reality it's rarely possible to completely isolate concerns (groups of schemas) under separate contexts. And then you'll have to alias models (schemas) awkwardly different, and it becomes impossible to tell what is aliased by the name only. What I found way clearer is traditional approach
App.Model.UserandApp.Context.Accountsundermodelandcontextdirs respectively.