Matthieu S.

Results 67 comments of Matthieu S.

It looks like this was fixed in the latest release of MockK (1.10.0)

Sure! I've made a repro repository [here](https://github.com/utybo/mypy-issue-89-repro). Instructions are in the README, let me know if you need something else 😄

Bug is still here, Gradle complains about not finding the packages declared using the Kotlin language when exporting them through the module-info file. @Burtan's solution's works flawlessly, huge thank you...

Multi-project builds seem to be broken in Kotlin even with the workaround. Projects that depend on other projects in the same multi-project build complain about missing modules.

There's already a small indicator on community made stuff. I don't think disclaimers can be easily added, is this good enough? ![image](https://user-images.githubusercontent.com/5175705/106338149-60e0ec80-6293-11eb-828e-b28a47d65ec7.png)

This is not possible until Kotlin's `context()` feature lands, because otherwise this requires defining an inline extension function (because of reified generic types) in `BodyDsl`

Pushing this back to an unknown date because this is extremely boring work, and I (currently) have no interest in working on this in my free time.

More precisely (this issue has been open for a year damn): - allow specifying qualifiers when using `putFactory` - add tests to ensure resolving qualified factories still works fine

Hi, thanks for your detailed issue! I unfortunately don't think there's much that can be done in Tegral without reimplementing parts of Swagger Core (which [is planned](https://github.com/utybo/Tegral/issues/55)) For a bit...

Idea for the step 3 of this whole plan, I think it would be better if we use the following behavior. In cases where we could have a fundef: -...