Julian
Julian
I experience also a freeze but already when application starts up. Here's a related issue on lwjgl issuetracker: https://github.com/LWJGL/lwjgl3/issues/619 The `org.lwjgl.system.Configuration.GLFW_LIBRARY_NAME.set("glfw_async");` crashes immediately when added to main with: ``` Process...
Workaround found is to define JSONSchema manually. I did as follows: ``` @JSONSchema({ description: '...', properties: { '{itemId}': { type: 'object', description: '', properties: { '{attributeName}': { $ref: '#/components/schemas/MyDto' }...
Is there a simpler way to annotate such complex nested types with routing-controllers-openapi? I have the feeling an annotation could solve this a lot easier for everyone.
Same issue, workaround I use now is to annotate every field with an appropriate annotation e.g. `IsNotEmpty()` for strings. The dependencies we use are: ``` "dependencies": { "@google-cloud/firestore": "4.15.1", "bcrypt":...
It's likely possible to define your custom schema with the @JSONSchema annotation. However I'm not sure how to do it exactly. Does anyone know more details here? See also: https://github.com/epiphone/class-validator-jsonschema#validatenested-and-arrays...
Workaround in general is to define the JSONSchema manually. I provided an example in #98. Also for simple strings I had troubles defining the type correct so I did this:...
I am confused. This doesn't work: ``` TMLoginManager *loginManager = [TMLoginManager new]; // paste here id classMock = OCMClassMock([TMLoginManager class]); OCMStub([classMock sharedInstance]).andReturn(loginManager); id loginManagerMock = OCMPartialMock(loginManager); // cut XCTAssertEqual([TMLoginManager sharedInstance],...
There has been an update now in GLFW, it is now implemented for windows (no macos support). Should we reopen this ticket so when GLFW 3.4 comes out the support...
@mlopatkin not really helpful. He should have provided an example to reproduce the error. But aside from that it's actually a gradle issue not a question how to use gradle....
I think it's easier if you commit it in your repo after merging the PR, but it doesn't really matter for me. Is it easy to do a release after...