TimefoldAI / TimefoldAI/timefold-quickstarts
Quickstarts should explain score by justifications and constraint matches
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 580
- Forks
- 173
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 39
Description
The score itself does not tell users why the solution is good or bad. Each quickstart should provide explanation by using constraint matches in the UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the quickstarts and their UI but no files or tests. Start by reviewing each quickstart's score display and how constraint matches are exposed; define the explanation shown for good and bad scores, then verify the affected quickstarts present justifications in the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100