Custom IDE inspections without plugins

Slides for jLove talk about inspections

Main supplementary repo: https://github.com/Jellymath/structural-search-and-replace
Settings repository: https://github.com/Jellymath/structural-search-and-replace-settings-repo
Video (link may change): https://www.twitch.tv/videos/1068087950?t=3h56m20s

Transcript

1. Custom IDE inspections for effective testing (and more) Alex Levin jLove 2021
2. About me • Senior Software Engineer • Mostly JVM dev, sometimes JS/TS • Assisting in Kotlin Telegram Community • Came from Norilsk • Living in Berlin
3. Agenda • Why? • Check example project • Naive approach • Less naive approach • What is Structural Search and Replace? (SSR) • SSR Inspections • Sharing your results
4. Why? • Migrate • Automate • Not spend billion years
5. Example project Our scenario: • Java project • Tests are migrating to Kotlin • Mockito -> Mockito Kotlin • Junit5 -> kotlin.test
6. Let’s jump into code! Link - https://github.com/Jellymath/structural-search-and-replace Branch to start - original-java-code
7. Stuff done so far • Checked project • Rewrite it manually • Use some regexes
8. Structural Search and Replace (SSR) • Regexes are nice but they are working with text • SSR is taking syntax/semantics into account • Java/Kotlin are covered • Scala is not :(
9. Back to code Branch to work with - adding-kotlin-libraries-in-advance
10. Stuff done so far (update) • SSRs • SSR Inspections • Export/Import functionality of SSR • Saving SSR inspections in the repo • Saving SSR inspection in the separate repo • Adding settings repo
11. Summary • SSR is cool • Sometimes prior knowledge is still needed • Not everything is smooth • Still easier comparing to writing custom plugins/inspections