When I wrap a Mojit in HTMLFrameMojit and I use ac.error() in a controller.server.js file, nothing is printed since, this.done('') is empty. Shouldn't there be a way to print the error message?

In the particular case where I hit this, I was trying to launch Mojito when there was already an orphaned instance running somewhere else. I'm guessing Mojito would have produced a very helpful error message, but the logging output was truncated in the midst of a long output line regarding loaded modules.

I'm assuming this is some kind of issue with un-flushed output buffers.

The particular form of this bug is pretty unfortunate since you'll almost always be very interested in the logging output just prior to any server failure, and that's the output most likely to get lost.

Even though the following command give error on using keyword as mojit name, but the mojit is still created successfully.

mojito create mojit this

These calls are frequently used and the callback parameters need documenting

The default error() function the composite plugin uses to handle child errors looks like this:

        error: function(err) {
            Y.log("Error executing child mojit at '" + this.id + "':", 'error', NAME);
            Y.log(err.message, 'error', NAME);
            Y.log(err.stack, 'error', NAME);
            // Pass back some empty data so we don't fail the composite
            this.done('');
        }

In order to allow the parent mojit to continue running, it passes back an empty string into ac.done(), but we should have a way to communicate child errors

There should be a standard for middleware unit tests so that mojito can pull them and run them with the app tests.

Instead of this:

"test static" : {
    "verbs": ["get"],
    "path":"/test/static/",
    "call": "test.static",
    "params": "foo=bar&foo2=bar2"
},

I'd like to do this:

"test static" : {
    "verbs": ["get"],
    "path":"/test/static/",
    "call": "test.static",
    "params": {
        "foo": "bar",
        "foo2": "bar2"
    }
},

Currently, you cannot specify any node options using "mojito start", such as --debug.

Because 'mojito start' no longer reads 'server.js', where the custom logging functions would be defined by the user.

Y instances are cached within the client controller context object by mojit instance guid so that many actions on the same controller can always occur on the same instance.

If all the views of a particular mojit controller are destroyed, that Y instance is never removed.

This is a possible memory leak.

Every time a mojit proxy's private _destroy() function is called, the client needs to do a check to see if there are any more mojit proxies that exist tied to that same instance guid. If not, it should notify the ControllerContext to clear the cache for that guid, and it should dereference the cached Y instance.

As documented, customized logging uses the YUI._mojito.logger.set('formatter', ...) method to set up a custom log.

This mechanism is throwing an exception.

Mojito needs a way to group various bits of code that -- when combined -- provide additional features to the platform. These extensions should be installable via npm, but should not be applied to all Mojito applications when installed. Mojito apps should identify which extensions they require within their configuration.

Dependencies:

The npm package for an extension should identify any dependencies on other Mojito extensions. At the application level, a requirement for one extension should automatically install any dependent extensions within that application.

configuration currently does not accept false or null values as stated on json.org

The handleClick Binder function is not documented in the Mojito docs.

Also Binder class doesn't seem to documented at all.

'mojito compile -e all' creates different output if the app directory is called 'mojito' than if the directory is called something else (no views or json)

In addition to being able to specify a different view template from the default (the action name), we'd like to be able to specify a different binder as well, in the case where we'd like to share a view template between two different actions, but with different bindings.

Mojito programmers write code that live in various contexts:

Mojito framework
Node.js
mojits
controllers / models
binders
objects - ActionContext, mojitProxy, this.config, etc.
addons / YUI modules
middleware
configuration - application.json, defaults.json, definition.json

Allow applications to define custom middleware components which will execute in the Express/Connect middleware stack. The actionContext and other Mojito components must be verified for correctness upon completion of all middleware component execution, prior to the final request handling steps.

Allow app-level config to be available in models, so that things like API
hostnames, etc.. can be stored in the config.

Example:

Y.mojito.models.foo_model = {

        init: function(cfg, app) {
            if(cfg){
                this.cfg = cfg;
            }
            if(app){
                this.app = app;
            }
        },

The test case for the "inter-mojit" application in the examples/developer-guide fails, when the link is clicked. It shows some error in firebug:

c is undefined
[Break On This Error] var receiverID = c["receiver"].viewId;

When having:
mojit/Foo/assets/css/skin.sam.css
mojit/Foo/assets/css/skin.caridy.css

after running: mojito compile rollups

the rollup.client.js will have only one of those two files, apparently the routine for hashing the filenames is not good.

I can see the files listed in the compile routine output, but somewhere in the middle they got discarded.

The workaround is just to use - instead of .

mojit/Foo/assets/css/skin-sam.css
mojit/Foo/assets/css/skin-caridy.css

and everything works as expected.

Patch submitted internally at Yahoo!

Mojito generated code uses Date.now() which is only present in ECMAScript e5 platforms.

For example, when the following url is fed to Mojito:

http://localhost:8666/yahoo.sites.loader/index.html?viewer=yahoo.samples.viewers.wheel_of_fortune_test#Leo

no content is shown and the server log gives an error.

Initially when the Mojito Client is initialized, the binderMap sent from the server is used to create MojitProxy objects, and each one contains a config object with 'children' if there are any. This state is only the original state of the page, so when any mojits are dispatched that create new binders on the page (and new MojitProxy objects), the state of the parent binder is not updated, and there is no way for mojits to know the current state of its children.

Mojit binders must be able to have info about their current child state in order to destroy their children, otherwise they can only destroy the children defined in the original page state.

This bug must be fixed before I can remove the automatic binder cleanup, because binders must be able to destroy their children programmatically (even those that have appeared after the initial page state).

In a model, I convert an object of objects to an array of objects like this:

var list = [];
list = Y.Object.values(this.feeds).sort(sortFeeds);

In the controller, I assign this array to an object and pass to ac.done() like
this:

var vudata = { //mustache template data
spaceid: this.config.spaceid,
tiles: []
};

//later
vudata.tiles = list;
ac.done(vudata);

Starting mojito and requesting the page crashes node

The getSub/setSub methods are very useful to read and write hashed key/value pairs. Please support this so the interface is more similar to the YUI3 Cookie class.

addCss
void addCss ( link , location )
Method for adding a JS file to the page.
^^^^

This should say "a CSS file"

when using group setting is not defined in dimension.json, for example, in application.json, changed the "environment:testing" to "environment:testing1", the error msg is as following:

✖ The settings group '{"environment":"testing1"}' has already been added.
Error: The settings group '{"environment":"testing1"}' has already been
added.
at Object._processRawBundle
(/usr/local/lib/node_modules/mojito/lib/libs/ycb.js:196:27)
at Object.read (/usr/local/lib/node_modules/mojito/lib/libs/ycb.js:35:26)
at Object._readConfigYCB
(/usr/local/lib/node_modules/mojito/lib/store.server.js:1959:26)
at Object._readAppConfigNC
(/usr/local/lib/node_modules/mojito/lib/store.server.js:1197:30)
at Object.preload
(/usr/local/lib/node_modules/mojito/lib/store.server.js:252:38)
at Object.addMojitoToExpressApp
(/usr/local/lib/node_modules/mojito/lib/index.js:134:15)
at Object.createServer
(/usr/local/lib/node_modules/mojito/lib/index.js:263:14)
at Object.start
(/usr/local/lib/node_modules/mojito/lib/management/utils.js:410:56)
at Object.run
(/usr/local/lib/node_modules/mojito/lib/management/commands/start.js:78:9)
at main (/usr/local/lib/node_modules/mojito/lib/management/cli.js:112:13)

✖ Mojito was not started!

Calling ac.done(data1, 'json') from client and server give different results:

From client: Got object
From server: Got json formatted data.

We should probably open up a function within the static handler middleware so users can provide massaging of responses for static files.

[Massaging of] Expires, Last-Modified, or any custom headers someone might want.

• I have a mojit that uses ac.composite.invoke() to create child mojits
• Each of these child mojits has a binder of its own. When clicking “Search” the XXX binder issues an mp.refreshView() call.
• The number of child mojit instances will vary from refresh-to-refresh (currently just using Math.random() to achieve this)
• Eventually if you hit ‘Search’ enough times, you’ll get a Javascript error on the client.

I am executing the example in the developer-guide - using_configs
When running on Firefox, I see the below error on Firebug:

Y.mojito is undefined
[Break On This Error] window.YMojito = { client: new Y.mojito.Client({

"mojito start" has a --context flag that accepts arguments like
"lang:es,environment:dev".

"mojito build" has a --context flag that accepts arguments like
"lang=es&device=iphone".

These contexts both filter into the system in different ways. "start" passes the arguments directly in code, while "build" uses the argument to generate a URL.

These flags should take the same argument, or perhaps use different names since they filter into the system in different ways. "build"'s context is really more of a set of parameters for the URL today.

They are currently renamed to .txt files. Need to update test.js CLI command to prevent these tests from being included in the test configuration during test coverage generation.

I have a library of functions that check URL parameters and so I called ActionContext.params.getFromUrl() twice:

1. in libary
2. in mojit controller.server.js

The code ran fine but when I ran "mojit test app ." on my app, this caused the tests to fail with the error:

Method getFromUrl() wasn't called the expected number of times.

if (typeof(props[key]) == 'object') {

should be

if (typeof props[key]) == 'object') {

HTML5 bundled apps need i18n support.

We made an addon and put it on app/addons/ac/

A test for it located on the sub-directory app/addons/ac/tests/ is successfully loaded and executed with the "mojito test" command.

But when the file is left on the app/addons/ac/tests/ directory, the "mojito start" command throws an error on server load:

YUI-INFO get: Loaded:
/home/julionn/host/mib/todo/addons/ac/tests/featureflipper.common-tests.js
ERROR nodejsYUI3:

ERROR nodejsYUI3: TypeError: undefined is not a function
ERROR nodejsYUI3: at CALL_NON_FUNCTION_AS_CONSTRUCTOR
(native)
ERROR nodejsYUI3: at Object.fn
(/home/julionn/host/mib/todo/addons/ac/tests/featureflipper.common-tests.js:7:17)
ERROR nodejsYUI3: at [object Object]._attach
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:7:5240)
ERROR nodejsYUI3: at [object Object]._use
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:8:2078)
ERROR nodejsYUI3: at [object Object].
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:8:693)
ERROR nodejsYUI3: at Object._finish
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:13:2497)
ERROR nodejsYUI3: at Object._onSuccess
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:13:2997)
ERROR nodejsYUI3: at Object.loadNext
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:14:654)
ERROR nodejsYUI3: at [object Object].
(/home/y/share/node/yui3/node_modules/yui3-core/build/yui/yui-min.js:13:4529)
ERROR nodejsYUI3: at
/home/y/share/node/yui3/lib/node-yui3.js:837:30
ERROR nodejsYUI3:

DEBUG Mojito HTTP Server initialized in 1293ms.

When the file is on the directory app/tests/, it is successfully loaded both on "test" and "start" commands. But its placement is odd: ac addons tests should be on the addons/ac/ directory, and not somewhere else.

Our suggestion is to make "mojito start" ignore either files on tests/ directories or ending with -tests.js, or both.

I tried moving the generated index.mu.html to another directory to see what would happen. In the logs I get:

MOJITO mojito-mu: Rendering template "undefined"

/home/y/share/node/mojito/app/addons/view-engines/mu.server.js:33
if (err) { throw err; }
^
Error: EISDIR, Is a directory

And the process crashes.

Got "mojitYuiModules is undefined" from dispatch.common.js

logger.log('Dispatching an instance of "'+(instance.id || '@'+instance.type)+'/'+command.action+'" with the modules: ['+mojitYuiModules.join(', ')+']', 'info', NAME);

To reproduce:

cd qetest/source/applications/frameworkapp/common
mojito start
http://localhost:4081/#LazyParent

index: function(ac) {
var roles = Y._AppUtils.getRoles(ac);
if(roles.indexOf('unknown')==-1) {
ac.partial.render({some:"data"}, "error", function(html) {

the problem is that the callback has 2 parameters, like: function(err, html).
err is null on success.

Here is my working sample:
ac.partial.render(response, 'preview', function(err, html) {
Y.log('renderer: '+html, 'debug', NAME);
});

Maybe the API doc for ac.partials can be improved, so that it also describes
the callback in more detail, i.e. which parameters to receive.

In certain scenarios, the server will crash with a Function.APPLY_OVERFLOW error in util.common.js. Will attach a stack and descriptions of the scenarios shortly.