Skip to content

core, plugins: capitalize log message casing#2929

Merged
julianoes merged 1 commit into
mainfrom
pr-casing
Jul 15, 2026
Merged

core, plugins: capitalize log message casing#2929
julianoes merged 1 commit into
mainfrom
pr-casing

Conversation

@julianoes

Copy link
Copy Markdown
Collaborator

Summary

Makes all log lines in the library start with a capital letter for consistency (following the Heartbeats from system ... timed out fix).

Where a line began with a bare identifier — a syscall, function, message, or field name — I prepended a descriptive word rather than capitalizing the identifier itself, so the token stays intact:

  • "getaddrinfo failed""Call getaddrinfo failed" (also tcgetattr, cfsetispeed, fs::exists, tinyxml2::LoadFile, ...)
  • "mission_request_int: ...""In mission_request_int: ..."
  • "metadataTypes not found""Field metadataTypes not found"
  • "current_metadata_path() called ...""Function current_metadata_path() ..."

Plain-English messages were simply capitalized ("command denied""Command denied", "version not found""Version not found", etc.).

Notes

  • Pure log-string changes across 24 files; no behavioral change.
  • Grep confirms no lowercase-starting Log*(...) lines remain in src/mavsdk.

Make all log lines start with a capital letter for consistency. Where a
line begins with a bare identifier (syscall, function, message or field
name), prepend a descriptive word instead of capitalizing the identifier
itself, e.g. "getaddrinfo failed" -> "Call getaddrinfo failed".
@julianoes
julianoes merged commit 41c1a08 into main Jul 15, 2026
52 checks passed
@julianoes
julianoes deleted the pr-casing branch July 15, 2026 21:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant