lundi 24 avril 2023

Design pattern for output string lookup [closed]

Suppose I have a program which is based around decrypting blobs to human readable format. I face the issue when each developer describes decrypted blob content as they understand it. Same applies to logging and error messaging.

So I want to unify language our app uses. Preferably in a way which allows me to give some files to support/ui guys/etc. so that they define what they wanna see.

I need to unify

  1. Error messages
  2. Logs
  3. Other user output including enum-to-string and bitfield/struct-to-strings kind of decryption.

I was thinking at some point of getting away with just a couple of maps, but I was wondering if there’s some good design patterns for that.

Aucun commentaire:

Enregistrer un commentaire