Skip to content

Report invalid developer base types cleanly - #161

Open
Bolt4243 wants to merge 1 commit into
dtcooper:masterfrom
Bolt4243:fix/invalid-developer-base-type
Open

Bolt4243 wants to merge 1 commit into
dtcooper:masterfrom
Bolt4243:fix/invalid-developer-base-type

Conversation

@Bolt4243

Copy link
Copy Markdown

An invalid base type in a developer field description currently escapes as a raw KeyError. That exposes an internal lookup failure instead of the parser's public error category.

Validate the decoded base type before constructing the developer field and raise FitParseError when it is unknown. The regression test uses a complete FIT byte stream with developer metadata.

Tests: full unittest suite, workflow flake8 checks, and coverage run with 93% total coverage.

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.

2 participants