Caridy Patiño comments

Results 457 comments of


                                            Caridy Patiño

Invalid value from ac.params.getFromUrl(key)

I presume this is a client side issue.

[docs] mojitProxy.invoke()

/cc @zhouyaoji can you take care of this?

Get error after calling mojitProxy.refreshView() in a composite mojit.

What version of mojito are you using? Can you provide a simple code to reproduce the issue?

Get error after calling mojitProxy.refreshView() in a composite mojit.

On Trello for investigation: https://trello.com/card/client-gh908-get-error-after-calling-mojitproxy-refreshview-in-a-composite-mojit/504e5e3b7cd1578456fc430f/325

mojitProxy.config not being updated after mojtiProxy.refreshView

Workaround, from Yi: ``` In controller: ac.done(data, Y.mix(meta, {yourVar: xxx})); In binder: mojitProxy.refreshView(params, function(data, meta) { var yourVar = meta.yourVar; }); ```

Better reporting of errors in config files

We can definitely improve error messages when it comes to invalid files and syntax errors. In the case of the comments, you can get use to use .yaml files instead...

Info-level Console Log Needed to Note that Mojits that are 'appLevel' Are Being Skipped

@drewfish can you check this? I'm not familiar with `appLevel` workflow.

locatorObj.ready could be a promise fulfilled after parseBundle() is done

I will also argue that the `__dirname` passed into `parseBundle` should be a property of the instance since we don't expect parseBundle to be called twice for a locator instance.

locatorObj.ready could be a promise fulfilled after parseBundle() is done

when can we get this rolling?

Tests fail on Windows (Cannot read property 'baseDirectory' of undefined)

good catch! we have a similar situation a while ago in locator, and @drewfish managed to avoid the verification of the root. For locator the root is actually the dirname...