Open rivendell10 opened 6 years ago
Hey how can I test the functionality of this? Is there a google calender somewhere that I can make sure the reservations are showing up correctly?
@patrickbeekman You have to login in with the developer google account and check the calendar. The account details were sent via Filelocker.
I have applied the changes and updated the push request
I don't get this error on my maschine. Can you check if the config file is initilized and contains the correct path? Did you download the client_secret.json and token.json files and put them into config/env?
I just tried to do this and got the same error message as @haietza I did download the secret and token files and put them in config/env. I'm going to mess around and see if I did anything else wrong. var secret = fs.readFileSync(CLIENT_SECRET, 'utf8');
is the line in question in calender.server.controller.js
On line 10 in the file you misspelled it as "secrete". const CLIENT_SECRET = config.clientSecrete;
but this didn't solve the issue for me =(
What does your config/config.js
file look like? I feel like this may be the issue because I am not understanding how CLIENT_SECRET gets populated
Updated development.js file at the filelocker. Now it should work
Sweet it worked for me, I needed to keep the typo in const CLIENT_SECRET = config.clientSecrete;
but it sent a Reservation request! How do we view the requests? It didn't automatically add it to the calender, I added a birthday from 4-5 today
Nevermind I see it on the website now!
I will fix the typo. It created a birthday event for today in the calendar.
@rivendell10 I see the reservation was added, but I entered 4pm to 5pm on May 8 and it added it at noon?
When the reservation is first created, it should have "Tentative" in the title. When payment is received, then it should be revised to take that out of the title.
I'm also not able to get the tests to all pass?
Also, the test.js file has 'api' in the google callback url and it should not. Each of us should revise that on our individual copies.
Resolves #31 config/env/client_secrete.json and token.json will be sent via Filelocker.