PatrickJS

@fesor can you include a link in the readme about it?

@fesor is this PR good?

what do you mean by resolve? are you talking about ``` es6 $stateProvider .state('home', { url: '/', template: '', resolve: { yourData: function(yourService) { return yourService.getAsyncPromise() } } }); ```

@santios here's an example `client/app/components/home/home.js` ``` es6 import angular from 'angular'; import uiRouter from 'angular-ui-router'; import homeComponent from './home.component'; let homeModule = angular.module('home', [ uiRouter ]) .config(($stateProvider, $urlRouterProvider)=>{ $urlRouterProvider.otherwise('/'); $stateProvider...

``` es6 $stateProvider .state('home', { url: '/', templateUrl: 'page.html', controller: PageController, resolve: { myData: function(){ return promise; } } }); ``` you need to inject your service and return either...

@martinmicunda this is solved in angular2 but you would handle it like this in a directive ``` es6 import template from './home.html'; import controller from './home.controller'; import './home.styl'; let homeComponent...

to resolve you need to - create resolves in state; - add a controller to the state - inject the data that you want to resolve in the controller -...

I think it makes sense to allow for anyone to toggle the DOM context standard you're proposing or at least allow for a way to use it. the problem with...

ok I actually built the react+angular thing but I didn't like it because it turned into it's own framework and I didn't want that. I also didn't like all the...

GoTH stack so Go+htmx