AngularClass/NG6-starter

Starter for Angular + ES6 + Webpack

Andrew Lombardi

@kinabalu

like your todo example, the way that was coded up, definitely like that a lot

Sergey Protko

@fesor

this is very large topic) I hate when developers just throw all data into big fat grid)

I will cleanup my todomvc a little bit on the next week

to make use some of angualr 1.5 features

Andrew Lombardi

@kinabalu

oh fun

i don’t like big fat grids either, but i lack the design / ux chops to really do anythign else sometimes

Sergey Protko

@fesor

@kinabalu there is always traid-off

it’s ok)

Andrew Lombardi

@kinabalu

i probably need to just hire a talented UX designer to wield some more effective design to my crazy ideas

Sergey Protko

@fesor

@kinabalu for many cases it just additional overhead. For example for crud-like control panels.

Andrew Lombardi

@kinabalu

@fesor it’s nice though, because you can tell when someone put the extra effort in to a design and the UX behind it

Sergey Protko

@fesor

Angular 1.5 landed in NG6-starter

Andrew Lombardi

@kinabalu

nice

@fesor i probably need to put together a test or example of this problem I’m having

but if I have a component which is making a Restangular call, and a second component kinda depends on the value returned from that call… is this possible?

Sergey Protko

@fesor

@kinabalu promises?

I use uiRouter’s resolvers and try to never get data from components

Andrew Lombardi

@kinabalu

@fesor oh, shit… yeah … forgot about that

@fesor refactoring is fun and illuminating so very often

@fesor do you have any examples of doing this? I think I may just google around to see if I find something, or see if it’s in the todo app

Sergey Protko

@fesor

todoapp is single screen app… I don’t see how I can add something like that.

I tried to find some more complex applications and didn’t found anything useful

Andrew Lombardi

@kinabalu

hrmm bummer, ok

Sergey Protko

@fesor

I had a crazy idea of writting UI for jenkins CI in angular))

Andrew Lombardi

@kinabalu

that’s … ambitious

but warranted, jenkins CI is quite shitty

Sergey Protko

@fesor

no, managing part like jenkins configuration would stay as it is. Only list of jobs, simplify jobs configurations and so on.

but I just had no time for such projects (

Andrew Lombardi

@kinabalu

yeah, i know the feeling

@fesor when using resolve, will the object be added to this?

Sergey Protko

@fesor

@kinabalu … are you talking about binding values to component controller?

Andrew Lombardi

@kinabalu

@fesor yeah, i’d like to use values that are promise based inside the controller and move ‘em out to resolve like had mentioned

Sergey Protko

@fesor

.state(’stateName’, {
     resolvers: {
          someData: someDataResolver 
     },
     controller: function ($scope, someData) {
         $scope.$resolves = {someData};
     },
     template: `<my-component some-data=“$resolves.someData”></my-component>`
})

Andrew Lombardi

@kinabalu

ahh I thought it was just resolve: { someData: someDataResolver }

and I actually thought using $scope wasn’t really done with NG6-starter

Sergey Protko

@fesor

@kinabalu yeah… I hate to use $scope… but uiRouter doesnt support auto-export resolved data to $scope so i need to handle it mannually

maybe in 1.0

ngRoute does it automaticly

Andrew Lombardi

@kinabalu

ngRoute is a bit more painful to use though, no? that’s why everyone kinda defers to ui-router

Sergey Protko

@fesor

well… it just doesn’t support nested views which makes uiRouter defacto stanrad solution

there is also angular-router, which should be cool… but I didn’t tried it yet

Andrew Lombardi

@kinabalu

@fesor is it possible to inject a service into the resolver flow? ordinarily I’d obviously have a class and use “ngInject”; in the constructor

Sergey Protko

@fesor

yes

resolves: {
    someData: function(someService) {
         return someService.getSomeData();
    }
}

Andrew Lombardi

@kinabalu

ahh and would you use “ngInject” within the function, or is it done automagically?

Sergey Protko

@fesor

well… can’t tell you) I just add ”ngInject” always)

just to be sure)

Andrew Lombardi

@kinabalu

haha

Andrew Lombardi

@kinabalu

@fesor trying to make the resolve stuff work, and ran into a slight issue:

        .state('accountsViewInfo', {
            url: '/accounts/info/:accountID',
            template: '<detail></detail>',
            resolve: {
                account: function($stateParams, accountService) {
                    "ngInject";
                    return accountService.getAccountById($stateParams.accountID);
                }
            }
        })

if I pass into the controller: account

    constructor($stateParams, $localStorage, accountService, account) {
        "ngInject";
        var self = this;
        this.accountService = accountService;

i get a can’t resolve provider error

Where communities thrive

People

Repo info

Activity