Expand bounded lab recurrence and alternating teaching weeks

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, nodejs
Domain
backend

Research direction

Read docs/PROJECT_CONTEXT.md and AGENTS.md, then inspect src/labs.js, test/, and the contract from dependency #31 before discussing the design with the maintainer. Start with the existing authorization, safe-error, and synthetic-fixture patterns. Done means fixtures cover bounded teaching periods, parity anchors, year rollover, Skopje DST, missing timezones, duplicates, and range limits, with ambiguous anchors and missing times left unknown.

Written by the indexing model from the issue text.

Description

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

Part of #28 · Target: Scheduling / v0.5

Goal and scope

Expand explicit weekly/selected-date/alternating-week rules only within known teaching periods and requested ranges. Require a known parity anchor and timezone. Generate stable occurrence identities and preserve evidence.

Implementation starting points

new occurrence resolver, src/labs.js, test/. 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 #31. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No guessing holidays/parity, unbounded recurrence or calendar synchronization.

Acceptance criteria and test plan

Fixtures cover inside/outside teaching periods, alternate-week anchors, year rollover, DST transitions in Europe/Skopje, missing timezones, duplicate entries and range limits. Ambiguous anchors stay unknown and missing times are never invented.

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 25m
Merged PRs (30d)
13

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.