Alex Garel

I would be in favor of keeping the history, that is act as a revert in git. That is : keep the faulty edit, but add an edit on top...

I don't think it would be handy to do this in JS. In our current settings it will be hard to test, easy to break. For a function like this,...

I also have this problem... this means some inaccurate votes ! On firefox 124.0.2 on Ubuntu 23.10.

Hi I bumped into this myself… I need it to display our OpenAPI schema which is indeed a bit complex.

https://user-images.githubusercontent.com/144788/216589254-c5529f9c-ed53-4287-9ca5-6d0bfb393261.mp4

Crypto are a bit of an ecology nightmare (at the time of writing). Personally I would not encourage this (I just express my opinion).

The way to go IMO is to always have barcode but with display none (and no schema if it's fake)

It depends when completion request arrive ... I fear this is deep into tagify to fix this.

@oyenuga17 can you fix the perl check ? It might be as easy as `make lint` and then commit / push the changes.

/update_tests_results