aurelia/Discuss

Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5

Greg Poole

@gpoole

I've got this in my little demo thing:

"*": "dist/*",

and yeah no you shouldn't have to

sorry that's in paths in config

it's pretty convenient but yeah it's not strictly correct I suppose

Roberto Wesley Overdijk

@RWOverdijk

And it might make for a pita once the standard changes

Greg Poole

@gpoole

I'm not sure if the System API is meant to support much configuration or if SystemJS does all of that as a "bonus"

Roberto Wesley Overdijk

@RWOverdijk

Becomes more strict. Then you can no longer update without removing all of those

That alias thing is a bonus

It's a feature that is needed to map your import calls to the directory in jspm_packages

And it can be abused for stuff like that

Oh, and map to dist/ so you can build

Greg Poole

@gpoole

I came from RequireJS where I was used to just doing that as a matter of course

Roberto Wesley Overdijk

@RWOverdijk

Yeah

require.js was a pita

Greg Poole

@gpoole

yeah you really feel the difference

Roberto Wesley Overdijk

@RWOverdijk

I still cry at night sometimes

Greg Poole

@gpoole

particularly with the optimiser

Roberto Wesley Overdijk

@RWOverdijk

And the fact that 70% of the bundled file size was requireJS

Greg Poole

@gpoole

most of the configs I kept feeling forced to write were never "quite right"

Roberto Wesley Overdijk

@RWOverdijk

Added with jQuery at the time, that made for one hell of a bundle, which didn't go well for 3G. Guh.... The web is becoming awesome

Mikko Vuorinen

@vuorinem

Hi, has anyone noticed that in Firefox the change.trigger for select-element is fired before applying the change to the value.bind, but in Chrome (and IE I think) it's the binding first then the event?

Tony Olsson

@Souldrinker

Nope, haven't tested that, but I noticed that when I used click.delegate rather than change.delegate the triggering of the binding and delegate was done in different order even between Chrome and Opera, but after changing to change rather than click I got consistent behavior and I'm pretty sure I tested that in Firefox also...

However I'm not really sure whats the difference between trigger and delegate ;-)

Greg Poole

@gpoole

trigger attaches the handler directly to the element and delegate waits for it to bubble up

Mikko Vuorinen

@vuorinem

Hmm looks like delegate works more consistently, thanks @gpoole !

Plunkr: http://plnkr.co/edit/OoSb3DNri16nCbKoPTyQ

Greg Poole

@gpoole

I think probably because the handler is executing later when you set it to delegate

sounds like a weird timing issue though?

Mikko Vuorinen

@vuorinem

Do you think it's safe to assume the binding has been changed when delegate fires?

Greg Poole

@gpoole

oh interesting I wonder if it's because aurelia internally is using delegates to handle the bind change

I bet that's what it is

I would've said that it shouldn't matter but if you bind directly to the element you're going to receive the event earlier than the delegated one at the document level

because your handler fires, then the event bubbles up to the document level where the aurelia binding stuff is handling it again

in that case I'd say it might just be coincidence or a browser quirk that your event handler was ever seeing the updated value

so yeah I'd say it would be safe to assume

I think strictly the event handlers should fire in the order they were registered

so aurelia's should be registered before yours are

Mikko Vuorinen

@vuorinem

That all makes sense now. Ideally I would be using valueChanged-handler rather than DOM events, but I have a repeat.for and the value is bound to another model's property.

Greg Poole

@gpoole

is valueChanged for when the actual object's value has changed?

Mikko Vuorinen

@vuorinem

that's if I have for example @bindable value in my VM, I'll just add valueChanged()-method to the VM.

Greg Poole

@gpoole

yep well to me it makes sense that you'd always get the updated value if you use a delegate

I think it's generally considered better practice to use delegates anyway, particularly if you're using a repeat.for since you'll only register one event handler instead of a handler for each thing in the list

Mikko Vuorinen

@vuorinem

Seems to work that way, and solves my issue with Firefox. Thanks for the help!

Greg Poole

@gpoole

glad it worked out!

derivo

@derivo

Hi, can anyone give an advice. I saw how Angular and Aurelia works, no questions for me, Aurelia rules. Now, I'd like to implement Aurelia into my Codeigniter project which has assets in root directory, template files in child folders. So from here comes questions: is Aurelia a solution for me (as for frontend) and how to make it work with php live project (because Aurelia has all files in one folder in example so wonder how to play with it)? Maybe someone can provide an example on any php solution, really got stuck with this thing. Big thanks)

stevies

@stevies

@derivo - it is not too hard to change the application directory structure. The Aurelia sample skeleton navigation project has everything in one top level directory, so most examples just follow that. But if you need to change folder structure, it is easy to do.

Roberto Wesley Overdijk

@RWOverdijk

Do you think Proxy will ever be accepted?

Giovanni Lovato

@heruan

I'm trying to catch errors in Aurelia plugin initialization and I found I can catch them in the failure callback of aurelia.start(), then I set up the failure callback as:

aurelia.start().then(a => {
    a.setRoot('index');
  }, a => {
    console.debug(a);
    console.debug(arguments[0]);
  });

and the weird thing is that the debug of a is HttpResponseMessage but the debug of arguments[0] is Aurelia; how's that possibile?

(My goal is to catch errors and a.setRoot('error') to display a ViewModel with the error message.)

Sam De Block

@SamDeBlock

probably with the arrow functions stuff, so that arguments refers to the top level function arguments

Where communities thrive

People

Repo info

Activity