There were some problems on various parts. Please see each commit messages for the problem explanations and fixes.
This will not work correctly unless we add redirect URL of the extension to Google API console. You can see the redirect url on the developer console when you open the new tab after installing the extension.
You can change the client_id in manifest file to 658048146602-dm9i4u3pl0hotu691jqjesa5sagg09h5.apps.googleusercontent.com to be able to test the calendar.(But the redirect url may change and this client_id may become useless too. We have to publish the extension to get permanent redirect url, I guess.)
How to install temporary extension to test on Firefox:
Build the extension with yarn build-firefox.
Navigate to about:debugging.
Click to Load Temporary Add-on button.
Select the manifest file inside dist folder and click to Open button.
That was my first Vue experience btw. I didn't touch so many Vue files but nevertheless, it would be great if I can get some review comments if something doesn't look like what it supposed to.
There were some problems on various parts. Please see each commit messages for the problem explanations and fixes. This will not work correctly unless we add redirect URL of the extension to Google API console. You can see the redirect url on the developer console when you open the new tab after installing the extension. You can change the
client_id
in manifest file to658048146602-dm9i4u3pl0hotu691jqjesa5sagg09h5.apps.googleusercontent.com
to be able to test the calendar.(But the redirect url may change and this client_id may become useless too. We have to publish the extension to get permanent redirect url, I guess.)How to install temporary extension to test on Firefox:
yarn build-firefox
.about:debugging
.Load Temporary Add-on
button.Open
button.That was my first Vue experience btw. I didn't touch so many Vue files but nevertheless, it would be great if I can get some review comments if something doesn't look like what it supposed to.
Fixes #12.