--allowHashUrls option silently does nothing

[Mr0grog]

The crawler has a documented --allowHashUrls option, but it doesn’t appear to do anything. Searching the codebase, I can’t find any references to it except for the argument parser, so it doesn’t seem to actually be used.

I had expected this to allow a seed I’d listed with a hash URL to get captured. For example, using the following config:

scopeType: page
allowHashUrls: true

seeds:
  - 'https://www.eia.gov/naturalgas/ngqs/#?report=RP9&year1=2017&year2=2017&company=Name'

Is this something that’s just not hooked up, or maybe a vestigial feature that was supposed to be removed?

The workarounds I’m currently trying are:

scopeType: page
include: ['.*']

or:

scopeType: custom
depth: 0
include: ['.*']

or:

scopeType: custom
depth: 0

seeds:
  - url: 'https://www.eia.gov/naturalgas/ngqs/#?report=RP9&year1=2017&year2=2017&company=Name'
    allowHash: true

(Side note: I’d hoped I could use allowHash on the seed with scopeType: page at the top level, but it looks like that scope type always prevents allowHash from being configured, which seems less than ideal.)