cqframework / cqframework/cqf-tooling
Smart Timestamping ValueSets
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 22
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Currently, running the ValueSet conversion in a repo results in phantom updates (where the only thing that has changed is the timestamp).
Describe the solution you'd like
It would be nice if the ValueSet conversion checked the output directly and only update the timestamp in the case of a new file or a change in an existing file.
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
Start by locating the ValueSet conversion entry point and the code that writes output timestamps. Compare generated output directly to existing files, then verify that timestamps change only for new or modified files and that unchanged conversions produce no phantom updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100