-
-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minimumBytes was not properly deprecated, breaking change #328
Comments
It's still there: Line 60 in b280b91
|
The usage of You are right @arciisine, it was already depricated since (#286, v13.0.0), and now it has been removed. You can pass any number of bytes @arciisine. There is no special number of bytes anymore, other then the total number of bytes of the file you wish to analyze. |
Just to reiterate the PR indicated it was deprecated but it was actually
removed from the public API and is no longer available to use.
I plan on updating my code to not rely on that constant, but the wording of
the change may surprise others as well.
…On Sun, Feb 9, 2020, 11:18 AM Borewit ***@***.***> wrote:
Closed #328 <#328>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#328?email_source=notifications&email_token=AAJUUL6J356DULA4DKKPXHLRCAUGPA5CNFSM4KSBWYFKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWQGD4XA#event-3020701276>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUULZWNL6635RIKMN2QHLRCAUGPANCNFSM4KSBWYFA>
.
|
Very good. Try to use fromFile() if possible. I updated the title of #319 and release description of v14.0.0. |
in 14.0.0 (a major release), minimumBytes was removed (not deprecated) (#319 ).
This has had a breaking change on code that relies on that constant being exposed. A proper deprecation path would be appreciated.
The text was updated successfully, but these errors were encountered: