I don't recommended that though because this._getCachedEventBubblingHandler is a private method and breaking changes to it might not result in a semver major bump because it is marked as private.
If you are storing it as an object type in state or session, you might consider converting it to state, you would get bubbling for free then.
Anyways, I'll post it because someone might know :)
My friend told me that when constructor is used in a function, Webpack spits out an error on the console saying Uncaught TypeError: _WEBPACK_IMPORTED_MODULE_0_ thatmodule__.a is not a constructor. He showed me the error. He said, in order to fix it, the word constructor should be replaced with initialize. The module being used and exported is ampersand-state and it's in src/profile/index.js.
import State from 'ampersand-state';
export default State.extend({......
// blah blah, code removed for clarityThen on the outer index.js(not src/profile/index.js), the code is
import Profile from 'src/profile';
export default module.exports = Profile;What are your thoughts on the constructor issue?
A commonjs import
Maybe webpack is trying to treat that as an es6 class when it isn't
I saw the error when I was playing around, but once I used the correct export syntax it went away.
good morning @RickButler :) that's what I see in our code :worried:
let me double check to make sure i'm telling the truth
yes it's what I see
the dev even added a comment before it saying "will both work in es6 and commonjs"
if you tried to use that in an environment that onyl understood commonjs style require module.export, then the import wouldn't work...
going back to the error I posted regarding constructor, what are your thoughts? I'm going to update my code copy to see the changes my teammate made. He said it fixes the error
i'll take a look at it deeper
i'll put a breakpoint
hello, i'm building my first ampesandjs app and having some trouble with a load on demand collection that I want to cross reference properties from another collection. Specifically i have an id field in my main collection, and I want to map that to a name field on the other collection by id reference. The solution I have works most of the time, but on occasion has no data in the second collection (I assume an async race condition causes it)
the render function on my page object is:
render: function () {
if (!app.itemclasses.length) {
app.itemclasses.fetch();
};
this.renderWithTemplate();
this.renderCollection(this.collection, collectionView, this.queryByHook('recipe-list'));
if (!this.collection.length) {
this.fetchCollection();
};
},
are there some examples of how to build an app with rest-collections and cross references? having no luck googling for them
oh, and the derived property on my recipe is:
ItemClassName: {
deps: ['Type'], fn: function () {
var itemclass = app.itemclasses.get(this.Type);
return itemclass != null ? itemclass.Name : '';
},
cache: false
}
The collection to return values
@StompyNZ It's hard to say without seeing where the two collections are declared/fetched etc. I can see the one
app.itemclasses.fetch() but probably need to see where they both get fetched etc. I assume the model with the derived ItemClassName is looking at the value of app.itemclasses before the fetch is done. You can either trigger changes on the models when app.itemclasses finishes fetch, or figure out a way to have you subview use a derived or some condition to waitFor both to be fetched.
@StompyNZ if you have the code on github I can take a look.
thats the specific page in question ;)
@StompyNZ I couldn't really test it, i get a lot of API failures, but something like this https://gist.github.com/RickButler/a0a1137e4dea01a2dbef4a37853ceb8f
the api server is a game server and very basic webserver that doesnt allow cors so cant make it available for testing remotely