Luiz Américo

I fixed this in my backbone fork. Look at the following commits: https://github.com/blikblum/backbone/commit/8054cdd740eb7d62489185ffb055ab9f97e0a7a1 https://github.com/blikblum/backbone/commit/e183cce5dc262ca91559c94230134db03ad40de2 Should not be hard to make a PR. Currently i'm on a slow internet connection so...

You can try https://github.com/blikblum/nextbone It uses ES classes, is tree shackable, integrates with webcomponents (out of box with LitElement, but can be any web component library), has a form bind...

This is one of the issues with ES6 classes. See https://github.com/jashkenas/backbone/issues/3560 for discussion.

FYI in my fork, idAttribute and cidPrefix are read from a static class field, i.e., a constructor property https://github.com/blikblum/nextbone/blob/master/nextbone.js#L549

defaults and Collection model can also be defined as static fields as well as methods > @blikblum To me, that feels very much like a workaround, but I'll admit it...

See also https://github.com/jashkenas/backbone/pull/4101

AFAIK is the first PR, all other were issues. Clarification: it does not introduce a new method `reset`. It adds an option. It could be used for arbritary values other...

> We'll probably have a weird problem with Collection#fetch's reset option, though. Can you elaborate the problem? It does not change behavior of existing code. The change is restricted to...

@kamsci i did the same in this [branch](https://github.com/blikblum/backbone/blob/nextbone/backbone.js) where i converted Backbone to ES6 classes

I think it will help a lot of people to migrate for more performant rendering strategy