Is your feature request related to a problem? Please describe.
When considering the adaption of trice tool my understanding was that I can assign my custom tags to messages and use those custom tags to route messages to different output channel. But it appears, that in order to create a custom tag I need to modify internal\emitter\lineTransformerANSI.go, which means changing the trice tool installation files, which makes my custom tags not transferable with the source code.
The particular use case I have, I want to log the changes that are done to device configuration and store it in separate place in external flash, so that these messages would be longer stored for tech support to use. So I wanted to introduce cfg: tag, which would be routed. I encounter this problem:
PS > trice insert -cache -IDMin 1006 -IDMax 6999 -IDRange cfg:1000,1005
2025/06/27 20:39:20 the with -IDRange applied name cfg is unknown. Please check var Tags inside trice/internal/emitter/lineTransformerANSI.go for options
Describe the solution you'd like
Possibility to define custom tags and version them together with the code
Describe alternatives you've considered
Currently, there is a list of predefined tags that I barely started using, so I just might dedicate one to my use case, but this is a workaround and has its limitations
Is your feature request related to a problem? Please describe.
When considering the adaption of trice tool my understanding was that I can assign my custom tags to messages and use those custom tags to route messages to different output channel. But it appears, that in order to create a custom tag I need to modify internal\emitter\lineTransformerANSI.go, which means changing the trice tool installation files, which makes my custom tags not transferable with the source code.
The particular use case I have, I want to log the changes that are done to device configuration and store it in separate place in external flash, so that these messages would be longer stored for tech support to use. So I wanted to introduce
cfg:tag, which would be routed. I encounter this problem:Describe the solution you'd like
Possibility to define custom tags and version them together with the code
Describe alternatives you've considered
Currently, there is a list of predefined tags that I barely started using, so I just might dedicate one to my use case, but this is a workaround and has its limitations