Preprocess hooks.json

[aarohmankad]

I was taking a look at the repo to see if I could add #9 (show preview of hook), and I noticed some aspects of processing the hooks could be improved. This issue can serve as an umbrella issue for the following improvements:

• Sort hooks.json on every pull request (using TravisCI?)
• Add unique keys to each hook on every pull request. We probably shouldn't use indices as a key.

[nikgraf]

@aarohmankad thanks for investigating! How do these two points help with issue #9 ?

[aarohmankad]

Oh these are just something I noticed while looking at #9, they're not dependencies.

[nikgraf]

@aarohmankad sorry, I was bit in a hurry last time. I totally agree on we shouldn't use indices as keys. Rather it would be better to use the repo url + hook name as this should be unique.

I'm opposed to sorting hooks.json since this probably would make it either harder to merge or contribute due merge conflicts.

[dmitryrn]

Why don't use hook.name as key cause there are no dups?

[nikgraf]

@dmitryrn there are plenty of duplicates e.g. useFetch