You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although #39 fixed the issue with bad values when setting encoder.dictionary, I discovered these bad values could still get passed in the constructor function. This was because the function looked to see if the value was truthy or not:
### [1.5.2](v1.5.1...v1.5.2) (2022-05-14)
### 🐞 Bug Fixes
* correct bug that allowed bad dictionary values to pass through the constructor ([bc6e6c7](bc6e6c7)), closes [#41](#41)
Contact Details
No response
What happened?
Although #39 fixed the issue with bad values when setting
encoder.dictionary
, I discovered these bad values could still get passed in the constructor function. This was because the function looked to see if the value was truthy or not:Changing the code to make it look for if that property is contained or not should fix the issue.
Version
v1.5.1
What operating system are you seeing the problem on?
Windows
What version of Node are you seeing the problem on?
16
Relevant log output
No response
Are you able/willing to make the change? (It's ok if you're not!)
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: