How deaglegross/sharpcoachplugin works
Based on our analysis of the file tree and the README, this project is a JetBrains plugin—namely, the “SharpCoachPlugin” for Rider and ReSharper. Its purpose is to provide features to “generate Mapping code from type A to type B,” among possibly other enhancements to C# development in the JetBrains ecosystem. The solution is multi-faceted as it uses both .NET (C#) and Kotlin code depending on the target IDE (ReSharper and Rider, respectively).
Project type and purpose
• This is a JetBrains IDE plugin built to improve C# development.
• It supports two platforms: one for ReSharper (typically .NET-based) and one for Rider (using Kotlin). The README clearly emphasizes plugin compatibility and versioning strategies for various Rider builds.
• The project also contains sample projects (“plugin_sample_projects”) and protocol definitions (in the “protocol” folder) that underline how plugin functionalities are exposed or tested.
File structure
• Notice top-level directories like “src/dotnet” for all the .NET code including core components, UI, tests, and “src/rider” for the rider-specific Kotlin parts.
• The “src/dotnet/ReSharperPlugin.SharpCoachPlugin.Core” contains detailed architectural layers such as:
– Builders (e.g., MappingCodeBuilder.cs)
– Components (e.g., MappingResultsStorage.cs)
– Helpers and TypeHelpers (for business logic on type mapping)
– Providers (both for C# element information and specific functionality)
– Models for mapping operation results and type definitions
• There is a separate “src/dotnet/ReSharperPlugin.SharpCoachPlugin.Ui” for the plugin’s UI pages and tool windows.
• The integration of Kotlin code under “src/rider” (i.e. plugin.xml configuration in resources and Kotlin actions/options) shows the Rider-specific implementation.
• Apart from the main code, you have supporting materials such as tests (under “src/dotnet/ReSharperPlugin.SharpCoachPlugin.Tests”), sample projects, build scripts (build.gradle, gradlew, publishing scripts), Gradle wrapper, and configuration files.
README for additional insights
• The README highlights build/publish commands, versioning strategies, and supported build numbers/ProductVersions. This indicates modularity and multi-branch versioning.
• It also directs attention to the “Mapping” feature documentation, hinting at detailed internal mapping logic that should be separately visualized.
Final advice
• Every major folder or module (i.e., Core, UI, Tests, Rider, Protocol, and Build tools) is represented.