The controller is currently responsible for loading dependencies all the way down the chain. This makes it difficult to load child view dependencies and opens collection views up to errors on the client side for unresolved views and templates.

When an error, such as a 404, occurs lazo replies using hapi's reply.view to serve an error view/template. This changes the HTTP code to 200. This behavior is incorrect.

Make rendering life cycle asynchronous. This would allow for the usage asynchronous template solutions and make it easier to handle the rendering of child and item views (pulling in dependencies at run time).

Determine strategy for resolving node modules including components. Currently the following strategy is used to resolve paths relative to the application, https://github.com/walmartlabs/lazojs/blob/master/lib/server/loader.js.

I've been trying to add socket.io listener to lazo server. There are a few issues I encountered:

1. It seems that you need to have an access to HAPI pack in order to install socket.io plugin. The only way I found to do that was via LAZO._servers.primary, which doesn't feel good.
2. Trying to require socket.io in Lazo app server-side fails for both LAZO.require and usual require. Is there something I'm doing wrong?

We are relying on and loading modules that should be left up to the application developer's discretion. This issue consolidates this effort.

• Remove Handlebars #165
• Remove jQuery #166
• Remove Underscore #167
• Custom Backbone Build #168
• Remove Async #169

Expose Hapi making it easier for developers to leverage it within Lazo. Ideally this should make it easier for Lazo to be multiple purpose, e.g., serve end points.

Documentation on server utilities says that they accept post methods. However, AJAX post results in forbidden.

To reproduce, see this branch: https://github.com/happypancake/lazojs-viewcollection-issue/tree/util-post

PS: is there any way to set content type on server utility responses? By default they return text/html.

When CSS link load results in a 404 it causes FF to hang because there is not an error back in the doc.updateCss method.

Originally started out with underscore, but lodash has nice features such as deep cloning. It would be nice to have a version for the server, client, and alternates for devices that do not need legacy support.

If underscore is removed or we do a custom lodash build then we need to create a custom amd build of backbone.

today it is required to include a template file (i.e. index.hbs) even it is empty.

Error templates are very limited. No styling can be applied. Investigate making error templates more robust. One implementation possibility is to have a default error component that would render the corresponding view for an error code, e.g., 500 would render 500.hbs applying all application CSS and JS plus any error component styling and JS.

When we navigate between routes that do not share the same layout or do not have a layout we are clear out the body. We should only remove the root controller's element and append the new root controller's element.

The reason being is that an application level widget may have appended markup to the body. This is commonly done for widgets that need to position themselves absolutely and have the highest z-index, e.g., a modal dialog.

In some cases it is necessary to fetch fresh data for a model between page navigations. It would be nice to able to set a property on a model or collection that would allow for this to happen on case by case basis with the default being to cache.

LazoModel.extend({
    cache: false
});

Currently delete method doesnt support request body for Delete method.

https://github.com/walmartlabs/lazojs/blob/master/lib/server/serviceProxy.js#L212

When the module 'app/bundle' is part of a combo handled response the module still loads because lazo is referencing it before the combo handled response has been processed.

The server loader needs to work with windows paths.
https://github.com/walmartlabs/lazojs/blob/master/lib/server/loader.js

Lazo has not been tested on windows. This issue blocks #58.

npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is most likely a problem with the lazo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! bin/postinstall

is it possible to make a cross site ajax call,

i have one server running on port 9000 which access a rest web service running on port 9080. when i call the service using jquery ajax with POST. while doing that my POST request becomes GET and I get a Method Not Allowed message in Chrome Console.

I have set jsonp and have set the response header as Access-Control-Allow-Origin with '*'

Comments and suggestions are welcome.

Thanks
Naren

When a model is in a collection and a CRUD operation is called on a model the Lazo base model should attempt to resolve a model id to an id parameter if one does not exist. it should also respect the idAttribute functionality in Backbone passing that attribute and its value as an id to the parameters if they do not exist already. An additional feature is to allow parameters to optionally be a function that returns a hash. This will ensure that all parameters make it to the model syncher.

It is documented and you even test for it but you never actually set the the property from app.json to LAZO.app

https://github.com/walmartlabs/lazojs/blob/master/lib/server/app.js#L141

today we need to mock a bunch of dependencies in order to be able to instantiate and render a view for testing purposes

Create application bundling utility for combo handling JS and CSS. Ideally this should be plug-able into other tools like Grunt and Gulp.

When I tried to load additional scripts using the app.json file OR in the LazoApp.extend({ js: [] }) it wouldn't take. I tried to access globals set in it and had no luck.

where is this in the backlog? It looks like you are presently pegged to 6.7.1. I'm starting to develop a new api to replace our existing restify based api with hapi v8. It would be nice to be using v8.x.x across the board as things have changed quite a bit in v8.

Relates to #62.

• Ensure all dependencies are up-to-date
• Ensure that package.json files for any direct dependencies that were created explicitly for lazo do not break npm shrinkwrap

use createModel to create a collection on the fly.

Pass the options { persistent: false; }. When the collection creates the actual model within the collection the option is no longer preserved as is it expected to do.

Tried to find a fix for it but if you can take a look at it would be great. Currently blocking us.

Heads up for a great work with Lazo!

Investigate removing underscore or replacing with lodash. Potentially have a custom build under a different module id that only contains the methods lazo relies on. If we do that then we need to ensure that Backbone contains all the expected methods.

Verify all use cases of nested component directory stuctures.
ie.
components
|-- c1
|--subcomp1a
|--subcomp1aa
|--subcomp1ab
|--subcomp1b
|-- c2

Context.prototype.setCookie and Context.prototype.clearCookie should accept de-normalized options before calling jquery-cookie or hapijs:

https://github.com/carhartl/jquery-cookie
https://github.com/hapijs/hapi/blob/v6.7.1/docs/Reference.md#serverstatename-options

Important: the default values also must be normalized.

Please, see issue #92. The problem is still there under Lazo 0.2.0

Would it be possible to bypass the tunnel in the case that an application would like to leverage CORS?

People keep running into application level conflicts when versions don't match for precompiled templates among other issues. I would prefer to just remove Handlebars from Lazo since it doesn't really need it. We can just use _.template to render the initial page and have it be the default template engine. Removing the Handlebars dependency will reduce the initial page weight and provide more flexibility especially when people are trying to port existing code.

it looks like @rodfernandez is making some progress documenting in the development branch. his documentation has helped me quite a bit as it his examples seem easier to consume for me than the wiki (thanks @rodfernandez)

I can't seem to find any documentation on testing a lazo based app. what are you guys using internally? i'm assuming i should be looking at documentation on how to test a backbone based app right?

Research implementing a default template solution that incorporates two-way binding on the client only.

we should add some CONTRIBUTING.md doc so that others can learn about how to contribute back.

something like https://github.com/vpulim/node-soap/blob/master/CONTRIBUTING.md

Create a generator to make it easier to spin up applications. Example commands:

create model model_name --syncher
create component component_name --controller --view
create application application_name

If a developer has a complex interface that is displayed temporarily, e.g., a dialog that contain a rich UI they should have the ability to specify the target element for ctl.navigate. The caveat being that if a target element is supplied that it is not part of the rendering context, i.e., it is not maintained when a parent view calls render. The developer should get a handle back to the create ctl, so that they can destroy it and its view.

Remove jQuery or a custom build under a different module id comprised of events and ajax only.

We should follow the same pattern as all other public APIs and use options.success/error backs for app initialization.

Hi, there is a TypeError : string is not a function on the client side within a collection view (loaded on a client) when that view reacts to changes in the underlying collection.

OSX 10.9.4 Chrome Version 37.0.2062.120

To reproduce the issue:

1. Check out lazojs-viewcollection-issue.
2. Go to localhost (page refresh)
3. Click more a couple of times - items will be added to the collection.
4. Go to Hello and then back to News. Try clicking More now - items will not be added to the solution.

It looks like uncompiled template is somehow used in this case.

There are a few screenshots below.

I'm sorry I couldn't be more helpful, I just discovered node.js and Javascript last week.

Implement child views that are part of the rendering life cycle receiving the calling controller's context. Possible interface would be child view hash that maps to data attributes in the parent view's template.

LazoView.extend({

    children: {
        viewPropName: {
            view: 'view_file_name',
            target: 'data_attr_val'
        }     
    }

});

See https://github.com/jstrimpel/hermes/issues/3

Explore ways to slice and dice what is required for initial page load and alternate builds targeted for different devices.

Better object mocking support for applications that use lazo, e.g., automatic generation of context object, factories for creating instances, etc. Open source mocks.

Remove async.

Using the lazo-navigate attribute on a link doesn't apply the defaultLayout. If specified in the layout route config it works as expected.

Currently, if the a view collection does not have an empty view assigned AND collection is empty, lazo will just silently timeout on server-side rendering, throwing Uncaught error: Invalid nested use of protect.run() from HAPI internals.

AFAIK, that is caused by the fact that controller._getEmptyViewInstance does not find anything and callbacks don't get fired.

May be lazo could guard against such common mistake by newbies by throwing an error or at least printing a warning?