Create a versioned synthetic MK/EN/SQ compatibility corpus

Open
#45 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
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js
Domain
testing-qa

Research direction

Read AGENTS.md, docs/PROJECT_CONTEXT.md, the existing parser tests, and fixture documentation; then inspect test/fixtures and the current adapters. Build reproducible, versioned synthetic fixtures with documented provenance and expected supported, partial, or unknown outcomes, including multilingual dates and malformed or prompt injection shaped content. Run the relevant offline tests, npm run check, and git diff --check; report any checks not run.

Written by the indexing model from the issue text.

Description

area:backend area:docs good first issue help wanted priority:medium type:feature

Part of #28 · Target: Release readiness / v1

Goal and scope

Organize small synthetic fixtures for supported HTML, separate sections, folders, PDFs, choices, assignments and announcement layouts. Add multilingual/date and unsupported/access-denied examples with expected outcomes and fixture provenance. Coordinate new adapter fixtures with their issues.

Implementation starting points

test/fixtures, existing parser tests, fixture documentation. 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

Ready to discuss/start independently against current master.

Out of scope

No real faculty downloads, names, student IDs, cookies, credentials or copied private course text.

Acceptance criteria and test plan

Offline fixtures are reproducible and versioned; expected supported/partial/unknown outcomes are documented. Include changed/deleted/malformed and prompt-injection-shaped content. Start with existing adapters; future adapters add fixtures as they land.

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.