Restore alias expansion in refinement diagnostic history #295

Activity

1. CatarinaGamboa

   added

   studyNeeded before the error-message user studyNeeded before the error-message user study

   on Nov 5, 2026
2. CatarinaGamboa commented on Nov 5, 2026

   

   CatarinaGamboa

   on Nov 5, 2026

   CollaboratorAuthor

   More actions

   Labelled study: the error-message study's specs use aliases (Port in the OpenNMS socket task, and an ImageWriteMode alias planned for the dcm4che ImageWriteParam task), and today a reader sees only the alias name.

   Example (main @ cd49fea), the ImageWriteParam spec with

   @RefinementAlias("ImageWriteMode(int m) { m == ImageWriteParam.MODE_DISABLED || m == ImageWriteParam.MODE_DEFAULT || m == ImageWriteParam.MODE_EXPLICIT || m == ImageWriteParam.MODE_COPY_FROM_METADATA }")
   ...
   void setCompressionMode(@Refinement("ImageWriteMode(_)") int mode);

   and a client calling wParam.setCompressionMode(4):

   Refinement Error: mode == 4 is not a subtype of ImageWriteMode(mode)
   

   Besides the structured data for the IDE, the CLI message could keep the alias name and add its definition, once per alias used in Found or Expected:

   Refinement Error: mode == 4 is not a subtype of ImageWriteMode(mode)
     where ImageWriteMode(m) = m == ImageWriteParam.MODE_DISABLED || m == ImageWriteParam.MODE_DEFAULT
                               || m == ImageWriteParam.MODE_EXPLICIT || m == ImageWriteParam.MODE_COPY_FROM_METADATA
   
3. CatarinaGamboa

   added a commit that references this issue on Nov 5, 2026

   Keep a static final constant's name in refinement errors (#490)

   ...

   327a0d1
4. CatarinaGamboa

   closed this as completedin #489on Nov 5, 2026