Databases
StackOverflow2013
Postsdbo
POHow to show feedback/error messages in a backbone application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to show feedback/error messages in a backbone application
    primarykey
    data
    text
    <p>I'm working on a simple CRUD proof of concept with Rails/Backbone/JST templating. I've been able to find a lot of examples up to this point. But after much searching and reading, I've yet to find a good example of how to handle these scenarios:</p> <ul> <li>info message: new item successfully added to list (shown on list screen)</li> <li>info message: item successfully deleted from list</li> <li>error message: problem with field(s) entry</li> <li>field level error message: problem with entry</li> </ul> <p>The Backbone objects are: Collection (of "post" Models) -> Model ("post" object) -> List/Edit/New Views (and a JST template for each of these views)</p> <p>So, I'm looking for a high level description of how I should organize my code and templates to achieve the level of messaging desired. I already have a handle on how to perform my validation routine on the form inputs whenever they change. But not sure what do with the error messages now that I have them.</p> <p>Here is the approach I'm considering. Not sure if it's a good one:</p> <ul> <li>Create a "Message" Model, which maps to a "View", which is a sub-view (if that's possible) on my existing views. This view/model can display page level messages and errors in the first three scenarios I mention above. Not sure if it's feasible to have a "sub-view" and how to handle the templating for that. But if it's possible, the parent templates could include the "message" sub-template. The message view could show/hide the sub-template based on the state of the message model. Feasible? Stupid?</li> <li>For the fourth scenario, the model validation will return an error object with specific messages per each erroneous field each time a "model.set" is called by form field changes. I don't want to interrupt the "model.set" but I do want to display the error message(s) next to each field. I want to know how to factor my edit/new template and Post model/view in such a way that I don't violate the MVC pattern. I.e. I don't want to put references to DOM elements in the wrong plage.</li> </ul> <p>Sorry if this is vague. If you're inclined to help, let me know what code snippets could be helpful (or other details) and I'll provide them.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to show feedback/error messages in a backbone application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to show feedback/error messages in a backbone application
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to show feedback/error messages in a backbone application
      1. USAndreas Köberle
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload