Databases
StackOverflow2013
Postsdbo
POClient Side validation on Backbone.js collection
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POClient Side validation on Backbone.js collection
    primarykey
    data
    text
    <p>I'm using backbone-on-rails gem and got the following: </p> <p>Model</p> <pre><code>class Crayons.Models.Color extends Backbone.Model validate: (attrs) -&gt; if attrs.colorname.length == 0 return "colorname can't be empty" </code></pre> <p>Collection</p> <pre><code>class Crayons.Collections.Color extends Backbone.Collection url: '/api/colors' </code></pre> <p>collection is created in a router</p> <pre><code> initialize: -&gt; @collection = new Crayons.Collections.Color() @collection.fetch() </code></pre> <p>Methods in ColorIndex</p> <pre><code> createCrayonId: (event) -&gt; event.preventDefault() val = new Crayons.Models.Color() val.on("error", @errorHandling); val.set(colorname: $('#new_color_name').val()) @collection.create colorid: val.get("colorname"); $('#new_color')[0].reset() errorHandling: (model, event) -&gt; alert(event) </code></pre> <p>I have a simple validation that shows an alert when the length is zero. However, after the alert box, the items are still being added to the collection because of <code>@collection.create colorid: val.get("colorname");</code> </p> <p>What can I do to stop the collection from adding the results in it when an error has been caught?</p> <p><strong>Update1</strong> Short term solution is below and it works but I'm unsure if its a correct way of doing things</p> <pre><code>ok = val.set(colorname: $('#new_video_url').val()) if ok @collection.create colorname: val.get("colorname"); </code></pre> <p><strong>Update2</strong></p> <pre><code>class Crayons.Collections.Colors extends Backbone.Collection url: '/api/videos' model: new Crayons.Models.Color() validate: (attrs) -&gt; if attrs.colorname.length == 0 return "colorname can't be empty" </code></pre> <p><strong>Correct way</strong> The validate function should be in the model and function that alerts the error should be initialized on the model. </p> <pre><code>class Crayons.Models.Color extends Backbone.Model initialize: -&gt; this.bind("error", @errorHandling) errorHandling: (model, event) -&gt; alert(event) validate: (attrs) -&gt; #your error validation goes here </code></pre> <p>Now the method in index is quite simple</p> <pre><code> createCrayonId: (event) -&gt; event.preventDefault() @collection.create colorname: $('#new_color_name').val() </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOmnipresent
    1. USOmnipresent
    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. POClient Side validation on Backbone.js collection
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POClient Side validation on Backbone.js collection
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POClient Side validation on Backbone.js collection
      1. This table or related slice is empty.
      1. VTUpMod
    1. COis your collection a collection of colors or something else?
      singulars
      1. POClient Side validation on Backbone.js collection
      1. USTom Tu
 

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