We have published one more mini-release Selenide 5.12.2.
Fixed annotations @Nonnull
… for some of
After upgrading to Selenide 5.12.0 some Kotlin users started getting compilation errors in their projects.
It’s because we marked all methods of
SelenideElement with annotations
@Nonnull, and Kotlin is sensible to them.
For the following methods we now changed
@Nullable annotation to
@Nonnull (because they never return null):
Now you can again put results of those methods to non-nullable variables (though such constructs seem to me a bit strange in tests).
See issue 1179 and PR 1181.
This setting didn’t work sometimes.
No we fixed it.
See issue 1172 and PR 1176.
We published Selenium IDE plugin which can export code to Selenide.
We will publish a separate post soon on this topic.
Huge thanks to Dmytro Stekanov for this historical moment for Selenide!