gravitas should contain logging equivalent options

[bandophahita]

When using a pacing function the option to change the gravitas needs to have the ability to pass in the equivalent terminology used by logging module.

@beat("msg", gravitas.INFO)

This would make using gravitas more accessible to folks who are already familiar with python logging.

[bandophahita]

It would be really nice if the gravitas argument accepted the adaptor values directly.

@beat("msg", logging.INFO)
aside("msg", allure.severity_level.MINOR)

We could still include gravitas.py values LIGHT etc which just point to the adaptor levels.

[bandophahita]

I wasn't considering the fact a test suite might use multiple adapters (adaptor? adapter? am I British?) at same time. Which seriously complicates trying to pass in the adapter value directly.

[perrygoy]

From our conversation though, it would be nice if each adapter supplied the appropriate equivalent, just keyed back to gravitas. For example, the StdOutAdapter can provide DEBUG = gravitas.AIRY, INFO = gravitas.LIGHT, etc. That would probably be useful!

[bandophahita]

I think this might be a good place to use enum. It allows the gravatas value types to still be int, while guiding the user to hint that it only accepts the values found in the appropriate enum.

[bandophahita]

I think what I want to do is allow users to pass in either the int value in accordance with whatever Adapter they are using or pass in the Gravitas(StrEnum). Is that too complex for folks to follow?

So the following two lines would be equivalent
aside("foo", gravitas=logging.DEBUG) # int
aside("foo", gravitas=Gravitas.AIRY) # Enum(str)

When they pass in the integer, the narrator just passes it through. This assumes the user knows better if they are using more than one adapter.
When they pass the Enum, each adapter would have it's own translation of the gravitas levels.