Basic QR Functionality

[jackklika]

Close #56

I have no experience with Vue and very little with npm, but for my own instance wanted to have some basic QR code functionality on the share page.

In this small feature, whenever the Share view is displayed, it will show a QR code that links directly to the download.

I'm sure this isn't up to par with the rest of the code, but it should be a starting point for someone that knows Vue best practices.

Let me know what you think, and I'd appreciate it if you could point out any problems or lead me on a path to making this small feature better and more in line with the project's vision.

-jack

[eine]

Hi @jackklika! Thanks for this PR. Overall, it LGTM, although I have not actually built it. Some minor issues:

• Can you please rebase on top of master to resolve the conflict with package.json?
• Is there any strong criteria to choose https://www.npmjs.com/package/qrcode instead of some other library/dependency such as https://www.npmjs.com/package/@chenfengyuan/vue-qrcode? Note that the answer is mostly FTR, in case we detect any incompatibility in the future.

[jackklika]

1. I'll check out the conflict and resolve it when I get a chance.
2. Nothing strong, besides that it has more downloads on npm, has two collaborators vs one, and the documentation made it easier for me to integrate it into the code as a beginner to Vue. Also, what does "FTR" mean? I'm not familiar with the acronym.

[eine]

1. I'll check out the conflict and resolve it when I get a chance.

Great. Whenever you can.

2. Nothing strong, besides that it has more downloads on npm, has two collaborators vs one, and the documentation made it easier for me to integrate it into the code as a beginner to Vue.

Good.

Also, what does "FTR" mean? I'm not familiar with the acronym.

For The Record. It is meant for anyone in the future checking the commit history and coming back to this issue; so that they have some brief explanation.

[jackklika]

I tested this on my personal instance and it seems to work.

Still hazy on the npm situation, so let me know if I resolved the merge conflict incorrectly.

[eine]

Thanks @jackklika!