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.

Sign up for GitHub

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

Jump to bottom

!!/report should !!/scan first #2289

Closed

longsonr opened this issue Jun 30, 2018 · 1 comment

Assignees

longsonr commented Jun 30, 2018

It seems that we're supposed to use !!/scan now either before or instead of !!/report.

Rather than having to remind occasional users of smokey to change their habits and have !!/report be a foot gun for them, why not...

have !!/report do a !!/scan first which falls back to !!/report if not detected
if you feel it necessary introduce a !!/report-no-scan command (or something like that) for the times when the user just wants to report w/o scanning.

that way those people used to using !!/report can continue to do so.

This idea was originally suggested here and here

iBug self-assigned this

Member

iBug commented Jun 30, 2018

Good idea. TBH I've though of this before and I just kept it personal. Now that someone brings this up, I'll make it work.

This was referenced Jun 30, 2018

Scan multiple URLs with one chat message #2290

Merged

Force scan with !!/report, merge !!/scan in #2292

Merged

iBug closed this as completed in

0a27181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment