explyt/spring-plugin

Component Inspection Describe the problem System.getenv("SOME_VAR") (and System.getProperty(...) for application settings) inside a Spring bean bypasses the Environment. The value cannot be overridden per profile, by @TestPropertySource / @DynamicPropertySource, by --args, by spring.config.import or by any external configuration source; it does not appear in /actuator/env; it is invisible to the plugin's property resolution, completion and navigation; and it breaks the moment the same setting is also declared in application.yml under a relaxed name (SOME_VAR vs some.var). Spring Boot already exposes every environment variable through SystemEnvironmentPropertySource with relaxed-name mapping, so @Value("${SOME_VAR}") or environment.getProperty("SOME_VAR") is a drop-in replacement. The pattern is common in applications that grew out of a plain main() and is a classic source of "works on my machine" configuration bugs. Describe the solution A new inspection in spring-core, SpringBeanSyste

Component Inspection Describe the problem In Kotlin, a Bean Validation constraint written without a use-site target on a primary-constructor property can land somewhere the validator never looks, so a class that appears fully validated effectively has no validation on the paths that matter: @Entity class Order( @Id @GeneratedValue val id: Long, @NotBlank var name: String, // ← lands on the constructor parameter only @Email var email: String, // ← same ) The decompiled Java carries @NotBlank/@Email on public Order(long, String, String) and nothing on the fields. Consequences: constraints are checked only when the object is built through that constructor; property updates are not validated (order.email = "bogus" passes); entities loaded/updated from the database are not validated, because Hibernate populates fields directly. This is the long-standing KT-19289 "Hibernate Validator Annotations Dropped" / KTIJ-31300 trap. It is still the default for the versions this

Goal Add the missing visuals so the README first screen and the wiki convey the value at a glance. The README hero drives the visit→star conversion, and the AI/MCP pages are a top traffic landing area but currently have no media. Current gaps Zero media: wiki pages MCP-Tools, Features, Usage. README hero is a static Endpoints screenshot; the differentiator (native context mode) is only a text link. Shot list P1 — highest leverage Native Context Mode hero GIF — click Load Beans → bean tree fills → open a @Conditional/profile bean → jump to its declaration (~15–25s, looping GIF). Use as README hero + top of wiki Native-Context-Mode. Static analysis vs Native mode side-by-side — a conditional/factory bean that static analysis misses (false "no bean" warning) → after Load Beans the warning is gone and autowiring resolves. Split image or short video. Wiki Native-Context-Mode + README "Why Explyt?". MCP tools in action — an AI agent calling explyt_find_spring_endpoi