For fixed-width inputs, do not automatically calculate a missing check digit, unless actually told to about postscriptbarcode HOT 11 OPEN

from postscriptbarcode.

I am traveling this weekend, but would like to add logging to the bwip-js public API to get a sense of how much current usage relies on automatic checkdigit calculation. This is a potentially breaking change for folks who rely on the public API for commercial use.

from postscriptbarcode.

Soliciting opinions on the above from those who have to handle fallout from downstream or cross-testing:

@gitlost
@metafloor
@semireg
@adamchainz

from postscriptbarcode.

This looks good to me and makes sense. Curious to see if @metafloor changes the API to match, or if defaults will be maintained along with a new negated boolean (skip-calculatecheck) to access this new behavior. Thanks for checking with us!

from postscriptbarcode.

Curious to see if @metafloor changes the API to match, or if defaults will be maintained along with a new negated boolean (skip-calculatecheck) to access this new behavior. Thanks for checking with us!

@semireg For API back compatibility, we could introduce a deprecated BWIPP option calculatecheckifmissing, which frontends could initially set unconditionally to restore the previous behaviour. This would allow for each frontend to transition at its own pace without need to create some tricky shim over the BWIPP inputs to fake up the old behaviour. I would be loathed to document this option (it's not something that I think general users should reply upon), and I would be tempted to remove it at some point in the not too distant future.

from postscriptbarcode.