Sébastien Ros

We want prevent doing dynamic translations (passing the string value in a localizer) even if this is the only solution that wouldn't break anything. Maybe we could introduce an attribute...

A new attribute for a new new functionality is less breaking IMO. > I'd keep things as close to how we do localization everywhere else as possible I think your...

> not to build a new developer experience that's different from the rest of the system Funcs are also different solution to define localizable string than just calling `S[]` also....

If we added a display name, what would we add in it, and where would it be displayed? Isn't the description sufficient in the UI?

This one is waiting for merge conflict fixes and an approval

Why is it blocking 1.5 release?

👀

I have thought about it too. And to drive a parallel with Timezones management, installing OC on a system should not behave differently based on the system's settings, as much...

The comment can be removed because it depends on the machine it runs on. I don't see any value there. What can be done with the benchmark is run it...

@MichaelPetrinolis so you are suggesting we only need to provide some pointers to document how to export logging to OpenTelemetry? And just add more structured log where necessary?