Export reviewed lab occurrences as an ICS file (optional v1 increment)

Open
  • Is something wrong?
#36 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, nodejs

Research direction

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then inspect the calendar projection and the dependency issue #35; implementation must wait until its contracts land and the design is discussed with the maintainer. Add an ICS serializer with tests and docs, covering escaping, line folding, timezones, stable UIDs, and unknown or cancelled entries. Done means exported fixtures pass an independent validator and the relevant checks listed in the issue pass.

Written by the indexing model from the issue text.

Description

area:backend area:docs priority:medium status:blocked type:feature

Part of #28 · Target: Optional / not a v1 release blocker

Goal and scope

Offer opt-in export of resolved occurrences with deterministic UID, timezone semantics, source links and explicit handling of unknown/cancelled/moved entries. Keep output private and let user choose export destination.

Implementation starting points

calendar projection, new ICS serializer, tests and docs. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Depends on #35. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No Google/Outlook synchronization, subscriptions, silent file overwrite, automatic exports or reminders.

Acceptance criteria and test plan

Validate ICS escaping, CRLF/folding, DST/timezones, stable UID updates and injection-shaped titles. Unknown dates/times cannot silently become invented events. Parse exported fixtures with an independent validator. This task may move after v1 without blocking the release.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
1h 20m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mahmutmft/courses-mcp

All issues in mahmutmft/courses-mcp

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.