You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Virtual symbols provide more interesting ways to have (and avoid) conflicts.
Adding additional messages and cleaning up the existing messages should help
users know what options they have to address conflicts.
This also puts all the conflict resolution in ReportConflictingSymbolsCommand
instead of spreading it across reference resolution as well.
returnMessage(null,Ids.DuplicateSourcesForOutput,"Multiple source files ({0}) have resulted in the same output file '{1}'. This is likely because the source files only differ in extension or path. Rename the source files to avoid this problem.",sourceList,outputFile);
returnMessage(sourceLineNumbers,Ids.DuplicateSymbol,"Duplicate symbol '{0}' found. This typically means that an Id is duplicated. Access modifiers (global, library, file, section) cannot prevent these conflicts. Ensure all your identifiers of a given type (Directory, File, etc.) are unique.",symbolName);
returnMessage(sourceLineNumbers,Ids.DuplicateSymbol,"Duplicate symbol '{0}' referenced by {1}. This typically means that an Id is duplicated. Ensure all your identifiers of a given type (Directory, File, etc.) are unique or use an access modifier to scope the identfier.",symbolName,referencingSourceLineNumber);
returnMessage(null,Ids.DuplicateTransform,"The transform {0} was included twice on the command line. Each transform can be applied to a patch only once.",transform);
thrownewInvalidOperationException("If a reference can reference multiple symbols, those symbols MUST have already been recognized as possible conflicts.");
0 commit comments