-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable/disable CalDAV calendar synchronization #1091
Enable/disable CalDAV calendar synchronization #1091
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1091 +/- ##
==========================================
+ Coverage 96.41% 96.42% +0.01%
==========================================
Files 640 643 +3
Lines 8163 8193 +30
==========================================
+ Hits 7870 7900 +30
Misses 293 293
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to my eyes, but didn't try with real calendars. Please find any testers to confirm it works well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me, but didn't test in real life.
Hi @bertrandda I've tested this PR with Google calendar No error in logs, but no event in Gladys Calendar ( Waited from 2H to be sure )
|
@VonOx There is no error in your logs & I just tried with Google calendar, it seems to work on my side. Can you check your |
Seem's to be a problem with my instance/google calendar. PR is ok ! |
* @apiName Enable | ||
* @apiGroup CalDAV | ||
*/ | ||
async function enable(req, res) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's weird to have an "enable" function that either enable or disable
Either you have a PATCH calendar API call (simple), or either you have a "enable" + "disable" route.
Pick one :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I chose to split in 2 routes because we need actions after disabling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comments :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Just one change, I just merged this PR: #1133
And we can no longer use this.context.intl.dictionary in the front, but instead we use a HoC component to inject the dictionnary as props :)
Could you make the change in this PR? (see the PR to see how to do it, it's pretty easy)
Thanks for your PR!
ef7b5d7
to
f4fa360
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code is great enough for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally, works fine!
Pull Request check-list
To ensure your Pull Request can be accepted as fast as possible, make sure to review and check all of these items:
npm test
on both front/server)npm run eslint
on both front/server)npm run prettier
on both front/server)npm run compare-translations
on front)front/src/config/demo.json
) so that the demo website is working without a backend? (if needed) See https://demo.gladysassistant.com.NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
Description of change
Add the ability to choose which calendars to synchronize in CalDAV integration.