STM32CubeMX possible bug/differences when generating USART code for STM32L0 and STM32L4

[After Forever]

When USART's "Overrun" is set as Enabled (the default):

Cube generates a call to LL_USART_DisableOverrunDetect for STM32L0

Cube doesn't generate any code concerning the overrun for STM32L4

When I set "Overrun" as Disabled:

Cube generates a call to LL_USART_EnableOverrunDetect for both STM32L0 and STM32L4.

I see two issues here - the reversed logic, and a bug (difference between L0 and L4).

[After Forever]

Forgot to mention that this is about the LL driver, and by reversed logic I mean enabling the "Overrun" option Cube generates Disabling code (if it generates at all), and vice versa.