Re: Marker design issue
Oops... On Tue, Oct 19, 2021, 09:29 sebb wrote: > What commons component is involved here? > > On Tue, 19 Oct 2021 at 13:37, Gary Gregory wrote: > > > > Hi All, > > > > I get bit by this every time I try to make my markers "fancy" so I took > the > > time this go around to open up a discussion :-) > > > > I want markers: > > > > Bob.children.John > > Bob.children.Jimmy > > Alice.children.Rose > > Alice.children.Sue > > (Never mind Alice.chidren.Bob) > > > > I want to turn off only "Bob.children" but I can't because "children" is > > effectively global and either can be defined in code with: > > Only Bob as it's parent, > > Only Alice as it's parent, > > Both Bob and Alice as parents (uh...?) > > > > This is a complete mismatch with hierarchical naming with have with > Loggers > > and confusing to no end, and not documented. > > > > Can/should we "fix" markers to behave like a clean hierarchy? > > > > Or, should hierarchical marker names be provided in some different way? > > With a different character than a dot for example? > > > > I was about to write some docs internal to a product at work to show how > to > > get logging to perform these fancy tricks but I won't until I get a > > clearer picture of what we can/should do for this type of use case. > > > > TY! > > Gary > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: Marker design issue
What commons component is involved here? On Tue, 19 Oct 2021 at 13:37, Gary Gregory wrote: > > Hi All, > > I get bit by this every time I try to make my markers "fancy" so I took the > time this go around to open up a discussion :-) > > I want markers: > > Bob.children.John > Bob.children.Jimmy > Alice.children.Rose > Alice.children.Sue > (Never mind Alice.chidren.Bob) > > I want to turn off only "Bob.children" but I can't because "children" is > effectively global and either can be defined in code with: > Only Bob as it's parent, > Only Alice as it's parent, > Both Bob and Alice as parents (uh...?) > > This is a complete mismatch with hierarchical naming with have with Loggers > and confusing to no end, and not documented. > > Can/should we "fix" markers to behave like a clean hierarchy? > > Or, should hierarchical marker names be provided in some different way? > With a different character than a dot for example? > > I was about to write some docs internal to a product at work to show how to > get logging to perform these fancy tricks but I won't until I get a > clearer picture of what we can/should do for this type of use case. > > TY! > Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Marker design issue
Hi All, I get bit by this every time I try to make my markers "fancy" so I took the time this go around to open up a discussion :-) I want markers: Bob.children.John Bob.children.Jimmy Alice.children.Rose Alice.children.Sue (Never mind Alice.chidren.Bob) I want to turn off only "Bob.children" but I can't because "children" is effectively global and either can be defined in code with: Only Bob as it's parent, Only Alice as it's parent, Both Bob and Alice as parents (uh...?) This is a complete mismatch with hierarchical naming with have with Loggers and confusing to no end, and not documented. Can/should we "fix" markers to behave like a clean hierarchy? Or, should hierarchical marker names be provided in some different way? With a different character than a dot for example? I was about to write some docs internal to a product at work to show how to get logging to perform these fancy tricks but I won't until I get a clearer picture of what we can/should do for this type of use case. TY! Gary
