Clean up warnings #1

Open
opened 2025-07-18 11:03:49 -04:00 by myrddin · 1 comment
Owner

The project was created in a rush, but now all the warnings need cleaned up. These should never have been committed in the first place, but you need to start somewhere and not versioning the code is worse.

The project was created in a rush, but now all the warnings need cleaned up. These should never have been committed in the first place, but you need to start somewhere and not versioning the code is worse.
myrddin added the
Kind
Enhancement
label 2025-07-18 11:03:49 -04:00
myrddin self-assigned this 2025-07-18 11:03:49 -04:00
myrddin added the
Priority
High
label 2025-07-18 11:06:04 -04:00
myrddin added this to the Conference ready milestone 2025-07-18 11:22:41 -04:00
myrddin added this to the Conference Badge project 2025-07-18 11:25:16 -04:00
myrddin moved this to To Do in Conference Badge on 2025-07-18 11:27:44 -04:00
Author
Owner

A lot of the warnings are from unused pieces of code within the bounded macros. That chunk of code has become too bloated anyways. This needs to be broken up into the different types: Bounded, Wrapped, and Clamped. It then needs to be placed in a library that can be used instead.

A lot of the warnings are from unused pieces of code within the bounded macros. That chunk of code has become too bloated anyways. This needs to be broken up into the different types: Bounded, Wrapped, and Clamped. It then needs to be placed in a library that can be used instead.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: myrddin/microbadge#1
No description provided.