Skip to content
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

Documentation for detect-new-buffer is missing #25

Closed
dskrvk opened this issue Nov 30, 2017 · 4 comments
Closed

Documentation for detect-new-buffer is missing #25

dskrvk opened this issue Nov 30, 2017 · 4 comments

Comments

@dskrvk
Copy link

dskrvk commented Nov 30, 2017

This was added in #7 but somehow got removed later. In addition, that original description was a bit terse - can you include an explanation and/or a link as to why this is bad?

E.g. amqplib requires using a Buffer ctor with an arbitrary String argument to send messages. I could add a suppression, but want to understand the intent of this check.

@dskrvk dskrvk changed the title Documentation for is missing Documentation for detect-new-buffer is missing Nov 30, 2017
@jesusprubio
Copy link
Contributor

Summary
The documentation for the detect-new-buffer rule was deleted from the README but the rule is still in the codebase.

Still relevant?
Yes.

Next steps

@jesusprubio
Copy link
Contributor

jesusprubio commented Mar 25, 2022

I can pick this one once we start to fix things.

@hedtkeCqse
Copy link

hedtkeCqse commented Jan 31, 2024

Is the reason this is dangerous nodejs/node#4660 ?
As a side note: new Buffer is deprecated now.

@nzakas
Copy link
Contributor

nzakas commented Feb 14, 2024

@hedtkeCqse yes, that's correct. I'll add that to the README.

@nzakas nzakas closed this as completed in 1bd0170 Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants