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
Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?
Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.
Description
Remarks emitted by command plugins using Diagnostics.emit(.remark, "This is a remark") are dropped, whereas the error and note behaviors print to the console
Expected behavior
Remarks should be printed to the console in addition to the other diagnostic types
Actual behavior
No response
Steps to reproduce
Create a command plugin from the builtin template
add Diagnostics.emit(.remark, "This is a remark") to performCommand
try applying the plugin to another package - remarks will not be printed
Diagnostics.emit(.warning, "This is a warning") to performCommand
The resulting warning is printed
Swift Package Manager version/commit hash
6.0
Swift & OS version (output of swift --version ; uname -a)
Apple Swift 6.0
The text was updated successfully, but these errors were encountered:
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?swift build
,swift test
,swift package
etc.Description
Remarks emitted by command plugins using
Diagnostics.emit(.remark, "This is a remark")
are dropped, whereas the error and note behaviors print to the consoleExpected behavior
Remarks should be printed to the console in addition to the other diagnostic types
Actual behavior
No response
Steps to reproduce
Diagnostics.emit(.remark, "This is a remark")
toperformCommand
Diagnostics.emit(.warning, "This is a warning")
toperformCommand
Swift Package Manager version/commit hash
6.0
Swift & OS version (output of
swift --version ; uname -a
)Apple Swift 6.0
The text was updated successfully, but these errors were encountered: