Problem

The intention action ConvertSqlFileToAnnotationAction was being registered multiple times for both Java/Kotlin DAO files and SQL files, causing a registration conflict error.

Relation

#451

Solution

Separated the single action class into two distinct action classes to handle each file type independently:

Changes Made

1. Created Abstract Base Class

   • AbstractConvertSqlFileToAnnotationAction: Contains common logic for SQL file to annotation conversion
   • Subclasses implement file type checking, DAO method retrieval, and provide their own display text

2. Split into Two Concrete Actions

   • ConvertSqlFileToAnnotationFromDaoAction: Handles conversion when invoked from DAO files (Java/Kotlin)
   • ConvertSqlFileToAnnotationFromSqlAction: Handles conversion when invoked from SQL files

3. Updated Plugin Configuration

   • Modified plugin.xml to register each action for its specific language context
   • DAO action registered for JAVA language
   • SQL action registered for DomaSql language

4. Added Localized Messages

   • Added separate message keys for each action to provide context-appropriate text
   • DAO action messages: convert.sql.file.to.annotation.from.dao.*
   • SQL action messages: convert.sql.file.to.annotation.from.sql.*

Benefits

• Eliminates multiple registration error
• Provides clearer separation of concerns
• Allows for context-specific behavior and messaging
• Maintains all existing functionality while improving code organization

Testing

• Verified that the intention action appears correctly when invoked from DAO methods
• Verified that the intention action appears correctly when invoked from SQL files
• Confirmed that SQL file content is successfully converted to @SQL annotations in both contexts