Skip to content

feat: remove the limit of term splitting #19

feat: remove the limit of term splitting

feat: remove the limit of term splitting #19

Triggered via pull request August 29, 2024 16:10
@hualethualet
synchronize #353
Status Success
Total duration 1m 3s
Artifacts

call-static-check.yml

on: pull_request_target
static-check  /  Get-Config
10s
static-check / Get-Config
static-check  /  Call-GolangCiLint
0s
static-check / Call-GolangCiLint
static-check  /  Call-CppCheck
34s
static-check / Call-CppCheck
static-check  /  Call-ShellCheck
0s
static-check / Call-ShellCheck
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
static-check / Get-Config
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
static-check / Call-CppCheck: src/views/termwidget.h#L71
Class 'TermWidget' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
static-check / Call-CppCheck: src/views/termwidgetpage.cpp#L27
Consider using std::find_if algorithm instead of a raw loop.
static-check / Call-CppCheck
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/