There is currently no mechanism with which to handle the debug flag for log output at the deserializer/serializer level, should be added to the base classes #20

New Issue

claunia · 2026-01-29T21:16:38Z

claunia commented

2026-01-29 21:16:38 +00:00

Originally created by @HeroponRikiBestest on GitHub (Jan 25, 2026).

Self explanatory, created at request.

Originally created by @HeroponRikiBestest on GitHub (Jan 25, 2026). Self explanatory, created at request.

claunia closed this issue

2026-01-29 21:16:38 +00:00

claunia commented

2026-01-29 21:16:39 +00:00

@mnadareski commented on GitHub (Jan 25, 2026):

Note for myself: This needs to be either at the interface or abstract class level. I would prefer not to have to require it for the static serialization handlers, but it may be good practice to have optional parameters defaulting to false be used to ensure that future wiring can be done safely.

@mnadareski commented on GitHub (Jan 25, 2026): Note for myself: This needs to be either at the interface or abstract class level. I would prefer not to have to _require_ it for the static serialization handlers, but it may be good practice to have optional parameters defaulting to `false` be used to ensure that future wiring can be done safely.

claunia referenced this issue

2026-01-29 21:16:45 +00:00

[PR #20] [MERGED] Fix wise version(?) check for pre-string bytes #45

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/SabreTools.Serialization#20