Derrell Lipman

That has to do with the future `check` feature to check against a JSDoc string. The code is not executed (it's inside of `if (FUTURE)` which is `false`), but the...

jsdoctypeparser was in npm-shrinkwrap but had gotten lost in package.json at some point, probably with a merge conflict. I replaced the `if (FUTURE)` with an environment test. There should be...

> can you confirm that you implemented the feature where `setXxx` accepts a promise? Yes. All preexisting tests pass, as do the extras I asked you to create for me,...

I'll update the release notes to be explicit that the new implementation uses Proxy, so qooxdoo 8.0+ will not run in JavaScript engines that don't support Proxy.

It's partially true. I've updated the documentation and the test. qooxdoo classes can not extend native classes, but native classes can extend qooxdoo classes now.

That's a really good idea, I think. It is unrelated to this PR, though. That would be a change to the compiler, whereas this PR touches the compiler only for...

> @derrell There is a plenty commented code and code snippets without language set. Could you fix them? Or should I? Likely, I want to keep some of them there,...

> @derrell I don't like the name "showFeatures". Previous variant (show) was not clear and obvious and this one even more make harder to understand what for this prop is....

> > @derrell There is a plenty commented code and code snippets without language set. Could you fix them? Or should I? > > Likely, I want to keep some...

Yes, deep debugging requires a bit of getting used to, but once you get used to it, you learn to quickly run-until-function-exit on some of the calls. It's not that...