Add support for parsing/stringifying fragment identifier

[Mark1626]

Fixes #220

Add a new option parseFragment, which will provide the hash in the parseURL result. The new option is to prevent it from becoming a breaking change

Seems Fragment Identifier is the technical jargon for it, let me know if it's ok or hash seems like a better choice

cc\ @sindresorhus

[sindresorhus]

The name is "fragment identifier", not "fragment". "fragment" feels a bit too generic.

Can you also add it to the readme?

[Mark1626]

@sindresorhus Done

[sindresorhus]

Can you fix the merge conflict?

[sindresorhus]

stringifyUrl() was just added: 1604958 I think it would make sense to support fragmentIdentifier there too so they're perfect opposites.

[sindresorhus]

@M4rk9696 Bump

[sindresorhus]

Bump

[Mark1626]

Sorry, got busy with some work. I've made the changes except the typing. Any further changes I'll get it done ASAP and we'll get this closed soon

[sindresorhus]

https://github.com/sindresorhus/query-string/pull/222/files#diff-0730bb7c2e8f9ea2438b52e419dd86c9R357 is no longer correct.

[Mark1626]

@sindresorhus Made the changes

[sindresorhus]

#222 (comment)

[Mark1626]

Made the changes

[luckymore]

@Mark1626 How about this feature 😂

excute

queryString.parseUrl('https://foo.bar?query=1#/hashpath?hashquery=1', { parseFragmentIdentifier: true })

now

{
    "url": "https://foo.bar",
    "query": {
        "query": "1"
    },
    "fragmentIdentifier": "/hashpath?hashquery=1"
}

expect

{
    "url": "https://foo.bar",
    "query": {
        "query": "1"
    },
    "params": {
        "hashquery": "1"
    },
    "fragmentIdentifier": "/hashpath?hashquery=1"
}