Phoenix Web Development

Designing our message functionality

Next, we need to determine what functionality should be tied to messages in our application so that we can figure out what code we should be writing in our context. While you can always just default to implementing full CRUD (create, read, update, delete) for each of your schemas, you may specifically want to avoid doing this. One good thing about not just implementing these by default is you standardize the API for your database models that other developers can see and interpret. Doing so allows you to specify safe boundaries for how to interact with various models (for example, there may be a database table of constants that you do not want the user to be able to modify). In the case of our application, ...