Daniel H. Peger

@frantuma, @HugoMario I hate to mention random maintainers here but is there any chance this issue and the linked PRs (https://github.com/swagger-api/swagger-core/pull/4105, https://github.com/swagger-api/swagger-core/pull/4106) will get some love anytime soon?

@frantuma, @HugoMario another 3 month later. Could someone perhaps have a look? The fix is non-breaking, straight forward and will add support for the same reference types supported by swagger.

@mirichan as far as I understand the kotlin sources in your example my PRs would address the `Option` types as well as [`ResolvedType.isReferenceType`](https://fasterxml.github.io/jackson-core/javadoc/2.7/com/fasterxml/jackson/core/type/ResolvedType.html#isReferenceType()) will return `true` for these types

Any updates on this?! From my understanding editorconfig and the related plugins are far from able to replace the IDE specific formatting settings for Java.

Another use case from discussion https://github.com/storybookjs/storybook/discussions/15779 I'm using button knobs to push items to an array that is used as component input: ``` export const defaultElements: string[] = ["test1", "test2",...

@RickHuizing would you mind to open a separate issue for your problem. Best with some MVCE to help in reproducing the bug.

> But it will take more time and discussion to think through the implementation. @tim-finnigan could you perhaps elaborate on what the key problems are with adding checksum support to...

@deepy thanks for replying. I saw that issue (https://github.com/srs/gradle-node-plugin/issues/299), but as it mentioned Gradle 5 I did not further look into the details. So it seems it's actually broken with...

Since I want to get rid of gulp anyway this might be a good reason to tackle this and use your fork afterwards...

@rpalcolea have you been able to resolve NodeJS with a current Gradle 6 build? See https://github.com/srs/gradle-node-plugin/issues/351