#emberjs

the route doesn't have a model

the route has the model hook because the route has access to the params

like dynamic segments, in case it needs to find a record with a particular id, use query params etc

as I was saying, to circle back to your question you usually want to use the controller's model

Figured out the currentUser->user stuff. So, anyways. Next fun thing. ember-validations directly on a model instead of a controller, y/n?

sometimes you might want to have controller-specific properties

like currentlySelectedItem for an accordion or whatever

Really nice progress :) https://is-ember-fast-yet.firebaseapp.com/

Since the proxying ObjectController stuff is going belly-up, does it make sense to still put validations onto the controller layer?

nuck: how's proxying related to validations?

The ember-validations stuff doesn't officially support nested object syntax for validations

It exists, but it's labelled with scary warnings

mupkoo: the beginning of the end

It also seems like controllers as decorators is going the way of the dodo

you mean flubarbs?

And the ViewModel stuff is slowly collapsing

haha right locks

locks: At the moment I have no controller. Is there a default in that case? (ps. the controllers page in the guide makes a lot more sense now, thanks)

rioch: ember generates one for you, yeah

I guess to be more specific, I have simple length and presence validations on a few fields on the App model, which should exist for both apps/new and apps/edit

I think it used to generate either ObjectController or ArrayController depending on the model

probably still does, or it'd break compat

Was about to say that yeah, it'd break compat to stop

nuck: components? O:D

locks: you've really helped me out, thanks for taking the time. I know my question was a bit basic :) I have enough information to continue with the guide now I think.

I'm watching CSI Cyber

I think my brain is withering away

At least it's not as bad as Scorpion

rioch: go forth and conquer the world

Did Glimmer just steal the logo from Redis

And color it blue

health kit

or what's the other one

That layered logo thing is becoming a trope

locks: :)

I'd make a multi-layered pun but the logos have me beat

Ugh

I'm currently building an OAuth2 provider for hummingbird.me and having to make so many tweaks to our app registration and I just realized what a pain that page for acceptance will be

I can either (a) boot a whole Ember app for all 5 seconds that page is up or (b) figure out how to cram a third role into our app somewhere between "API" and "Ember"

brb throwing computer in blender and retiring from programming. I'm gonna go herd sheep or something nice and serene

"most people don't know but TSA keeps all xrays for a week"

don't you love freedom

locks: Most people don't know but the NSA keeps all those xrays for a decade after that week

:>

nuck: OAuth2 by itself isn't a complete nightmare, but doing it on javascript apps <3

locks: Yeeeaah

Like it's not too bad from a client perspective honestly

weeelll

it encourages weird behaviours

It redirects back to you with the hashurl and you rip it out and stuff

SoundCloud uses a popup, but I'm sure you could do just as well having it redirect back inside an iframe and then postMessage it to the outer environment

Hell you could probably do neither of those

But from a provider perspective, OAuth2 is even worse

how so

Most clients only deal with one or two of the flows

OAuth2 has a total of 5 main flows

how else besides popup or iframe

for a SPA app I mean

locks: Just check the hashurl on app boot

Your app redirects to them they redirect back

sounds very hacky

It causes a reboot

Which is shitty

yes

But it's still technically possible

and not always "possible"

Yeah

The iframe or popup approach is much better

But from a provider perspective you deal with all four flows and their slight oddities

the popup one is still weird

and like I said, encourages weird behaviours

like using popups xD

They tried to make a distinction between resource server and authentication server

By having the auth server issue codes which the resource server trades for tokens

But some of the flows completely destroy this distinction

The auth server has to give a token in the implicit (SPA) flow

It shouldn't have to deal with tokens but it does there

Still, the thing I'm most worried about is the app boot times for the OAuth2 "Do you accept this app to be your lawfully wedded wife?" page

I mean, Ember isn't exactly speed gonzales at booting

it will be nuck

it will be

:)

FastBoot, yeah

But I'll believe it when I see it

Ember is notoriously ADHD

what?

They'll do 80-90% of the work on something, then realize something else which tied into that, and go do that

And it just takes forever to do the original work because all the spinoffs suck time

it's called developing software :P

It's called being ADHD

I'm guilty of it too

if you say so

It's the good ol' rabbithole

Or... whatever-our-mascot-is-hole

WTF is the mascot even?

tomster

What is a tomster

hamster?

no

it's a tomster

hamsters can't program silly :p

a hamster mascot would probably be dangerous too

I mean, hamsters have a tendency to do a lot of work to get nowhere ;(

That's not something you wanna be associated with!

that's just a metaphor for IT

We need an animated tomster-wheel which spins as the core team devs type code

CSI is such a microcosmos of USA culture

dawson creek kills one person per episode

nothing of it.

I hope you mean microcosm, because microcosmos sounds like the galaxy on orion's belt

it's 9am

I hope you just woke up and didn't stay up all night

0 forks given

Y-you are MIT licensed right?

better run an AV

But I didn't even compile you yet D:

I don't think I've seen a black/white hat over 22yo yet

in this show

locks: The only person over 22 is the girl who makes the visual basic gui to backtrace the culprit's ip address

the writing in this show doesn't make a single thread of sense