Skip to content

Commit 9fda3e3

Browse files
authored
[move-compiler] Print request for linter feedback if linter warnings present (#13795)
## Description We would like to present to the developer a place where they could provide feedback on the available linters, with the information about how to report feedback being immediately available whenever the linter warnings are generated ## Test Plan All existing tests must pass plus manually tested that the message gets printed. --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes When linter warnings get generated, information about a place where the feedback on linters can be provided will be printed alongside the warning messages.
1 parent 612d7ce commit 9fda3e3

File tree

1 file changed

+6
-0
lines changed
  • move-compiler/src/diagnostics

1 file changed

+6
-0
lines changed

move-compiler/src/diagnostics/mod.rs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -288,6 +288,12 @@ impl Diagnostics {
288288
}
289289
v
290290
}
291+
292+
pub fn any_with_prefix(&self, prefix: &str) -> bool {
293+
self.diagnostics
294+
.iter()
295+
.any(|d| d.info.external_prefix() == Some(prefix))
296+
}
291297
}
292298

293299
impl Diagnostic {

0 commit comments

Comments
 (0)