Enforce maximum information capacity limits about angular-qrcode HOT 2 CLOSED

It seems to me the problem is actually a little more complex. It is (now) possible to dynamically change the error correction level and produce an invalid configuration. Is this the case with version as well?

Maybe the most sensible thing to is to do a pre-render check if the data is renderable and if not fire an event (edit: a callback) saying what the problem was (like, "you cranked the ecl up too high", but in a machine parseable format).

from angular-qrcode.

Thanks for your comment, it really helped, I've implemented the check as you suggested :-)

Also emitting an error event, so leave it up to the containing application how to deal with these.

from angular-qrcode.