aekidna

something like that, yes. appalling, I know. I'm in the middle of testing my framework and dust is plugged in for the templating side. It's working, so the hack is...

Correct. Let's say something like this: ``` dust.dataResolver = function(context, path) { return context.prop(path); } ``` where the default dust.dataResolver is the current dust implementation. There also should be some...

A use case for the iteration feature is an object that implements the ES6 [Symbol.iterator] protocol

@sethkinast Did you have a chance to think about this feature req?

Hey Seth. Thanks for getting back to me on this. I don't have full understanding of the inner workings of dustjs, therefore any submitted code would be inadequately implemented. I...

Aw, forgot to ask. Would you mind tagging this a feature-request? Cheers On 6 May 2016 at 08:00, Seth Kinast [email protected] wrote: > No problem, will investigate it in the...

@pantaluna That would be the proposed idea, supporting dictionaries/collections that cannot be natively enumerated, i.e. don't expose the values through own-properties. The extra object you're creating for your maps points...

> Why hasn't this been merged? Not sure. Try contacting the main contributors

Built locally. It looks like https://github.com/editor-js/image/blob/e26b3e7c106486d2d776219e18cd125469991a25/src/index.js#L303 is not initialising the tunes defined in actions in the `data` setter. When changed to ```js Tunes.tunes.concat(this.config.actions).forEach(({ name: tune }) => { ``` the...

Having the same issue. No access to meaningful error log. Only showing ``` unable to connect to isolate, terminated 2022-09-05 08:34:50 ``` And by the way, the Log UI generally...