Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/pandruszkow/o365-graph-api-md
A Markdown-based read-only client for the Microsoft Graph API (Office 365 API)
https://github.com/pandruszkow/o365-graph-api-md
Last synced: 26 days ago
JSON representation
A Markdown-based read-only client for the Microsoft Graph API (Office 365 API)
- Host: GitHub
- URL: https://github.com/pandruszkow/o365-graph-api-md
- Owner: pandruszkow
- License: apache-2.0
- Created: 2021-09-21T23:06:03.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-09-21T23:32:02.000Z (over 3 years ago)
- Last Synced: 2024-11-06T17:30:31.400Z (2 months ago)
- Size: 6.84 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# o365-graph-api-md
A Markdown-based read-only client for the Microsoft Graph API (Office 365 API)
Goal 1: speak to the Microsoft Graph API to read calendar meetings, and output them as Markdown files.
Goal 2: read Markdown files and be able to react to changes within them. Changes to Markdown files marked with an item UID corresponding to a known O365 meeting should write those changes to the cloud unless the ETag changed in the meantime (in which case do the default Palm thing and duplicate, or just ask the user). If a Markdown file describing an item UID for a known O365 meeting disappears (or has a property like "Deleted: true" appended to it), the cloud sync should detect that and ask the user to confirm the deletion (nicely in a bulk list, if the user does a lot of deleting so we don't end up with a hundred popups one after another). Maybe store some cloud-specific data, ETags, timestamps and other metadata beyond the basics that's immediately useful into a SQLite database (or make the SQLite the master store, and the export/import/change process only projects the data onto Markdown outputs/inputs). Any sync features should be robust. Lack of support for a sync functionality is better than allowing it to happen in a way that corrupts, skips or mangles data in another way.