I have test for creating activity name "test". At the first time it doesn't have any error. But when I create the new activity name "test" which time is not config with the first one. It's return this statement.

Now follow status is handle for multiple calendar in one user.

changing:

1. is_valid now checking calendar_id too not only user as before.
2. calendar is new foreign key in fs model.
3. fs API now provide followed_calendar and followed_calendar_slug

problems: there are one problems in test_me I could not find calendar_id and calendar.id can't seem to work so I just randomly put 1 integer for those follow_post test that require follow_calendar.

Event detail collect detail from FullCalendar event data maybe in the next iteration have to change to collect from backend database if want to show additional data such as description, tag, etc.

I have already implemented the create event method in a popup form. Also, a little improvement to the look of the view page. Is it ok to merge, or I need to discard template changes in ./src/App.vue to reduce conflict, and wait for the next Iteration?

I’ve already made these improvements.

• Create a global style and color file to be use in future feature(customizable template)
• Add search to nav bar and move nav bar to the appropriate file.
• Fix bugs in required input in form at Form.vue and RegisterForm.vue.
• Improve overall app template and disable some unused templates.

Is it ok to merge?

bug fix in follow tags

• follow tag is now checked from the owner of that calendar (id of the calendar in each event).
• when the user goes to the calendar that does not belong to them, the tag and event color appears in the normal gray follow style.

Now you can right click on event detail (sidebar) to edit or remove your event

There are problem when right click followed event it sneaky peaky for a milli sec. Hopefully to fix it in the next iteration.

Create button for Google. Now users can log in with a google account. From now token will new generated when the user login in and destroyed when the user logout.

Like title, now API for calendar event list will return 404 for not exist calendar, but our front end section does not handle this scenario. So it still lead to empty calendar page, not the 404 page.

This is example for http://localhost:8080/calendar/does-not-exist-calendar in console: GET http://127.0.0.1:8000/api/calendar/does-not-exist-calendar/ 404 (Not Found)

Update:

• Fix surname not found in google oauth.
• Fix setting debug type cast.
• Fix invalid image types (other than jpg, png, jpeg)

Recommend

• There are some local variable in front end that can be extact to outer setting file (eg. media path, cors path).

• The Following function now shows the user image and user description in the sidebar.
• Move sign in/ login with google button in a more appropriate place.
• Add alert when user tries to sync google event but doesn’t login with google.
• Minor templates improve in the user setting page.
• Minor bug fix in tag when user does not login.
• Set time delay on page load.