Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

The current tui graph mode only shows "total" by default, but it could show more fields from the command line option -f.

It'd be better to provide a way to customize fields in graph mode in interactive mode. I think f key can be mapped for this purpose. It could show a new box window just like h key for help message, then provide check boxes for each field.

Out of scope during Twitch Series but a nice to have feature that can be implemented

Booking is not currently using Subscription, and it could be done by leveraging parametrized Subscriptions.

Tasks to complete in order to implement this feature:

• Modify onUpdateBooking Subscription to include customer and status
• Implement onUpdateBooking subscription in the Fron

Feature Request

Crates

tracing::instrument

Motivation

The tracing::instrument proc macro is incredibly useful, and the docs encourage users to use it, as well as set a level. Not all users read documentation, so many use defaults. (Like me)

By default, they seem to decorate at all logging levels, which can impact performance for users in unexpected ways.

We met thi

Requirement - what kind of business use case are you trying to solve?

Our traces contain data that is covered by GDPR (european user privacy regulations) and, thus developers do not have direct access to all traces. If an error occurs, relevant traces has to be filtered out and the relevant ones are forwarded to the developer.

Another use case:
It would be nice to just attach files with