You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using CallsiteParameter.MODULE in CallsiteParameterAdder, it's a bit too vague for my tastes - for example, a module named config has no meaning unless I know what package it's referring to. For example, I may have a module called foo.bar.config and another package could have a module called baz.buz.config, and it would not be possible to tell the difference with that value currently.
I know that there's CallsiteParameter.PATHNAME, but that's overly verbose - although I guess I could transform it to be something more palatable... At the end of the day though, it would be nice if there was a CallsiteParameter that would just print out foo.bar.config.
The text was updated successfully, but these errors were encountered:
Those values and behavior are based on stdlib logging – how do they handle it?
poorly.
zero tolerance for deviation or extension. I have a patch for this (new provider), but waiting for my last pull because I'm sometimes lazy and potentially forgot to branch.
When using
CallsiteParameter.MODULE
inCallsiteParameterAdder
, it's a bit too vague for my tastes - for example, a module namedconfig
has no meaning unless I know what package it's referring to. For example, I may have a module calledfoo.bar.config
and another package could have a module calledbaz.buz.config
, and it would not be possible to tell the difference with that value currently.I know that there's
CallsiteParameter.PATHNAME
, but that's overly verbose - although I guess I could transform it to be something more palatable... At the end of the day though, it would be nice if there was aCallsiteParameter
that would just print outfoo.bar.config
.The text was updated successfully, but these errors were encountered: