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
Or if there's a smarter way to do this because I find myself either making a "Concern" that does this automagically or manually translating the name and upcasing it. Both of which seem...unrubyish.
I'm more than happy to provide code and tests and such, I was just making sure this hadn't been considered and discarded previously. In which case apologies for wasting your time.
The text was updated successfully, but these errors were encountered:
Not a bad idea, minus hard-coding of the naming convention converter: the conversion from an option name to ENV variable should be extensible by a class, for example:
option%w{--beep-boop},"VALUE","the beep and the boop",:env_mapper=>EnvironmentMapper.newclassEnvironmentMapperdefcall(value)"FOO_#{value.to_s.upcase}"endend
Hi
Long time listener, first time caller.
I'm wondering if anyone is opposed to having the ability to have:
translate to
the algorithm for which would be taking doing
plus allowing overrides via the traditional way as to not break existing stuff. This would be similar to how
delegate
is done in railshttps://apidock.com/rails/Module/delegate
Or if there's a smarter way to do this because I find myself either making a "Concern" that does this automagically or manually translating the name and upcasing it. Both of which seem...unrubyish.
I'm more than happy to provide code and tests and such, I was just making sure this hadn't been considered and discarded previously. In which case apologies for wasting your time.
The text was updated successfully, but these errors were encountered: