sillsdev / sillsdev/languageforge-lexbox
Activity preview: want to compare before/after, not compare with current version
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the feature
While working on a demo of FW Lite, I was making many changes to a single entry. I found that while the comparison of "Here's how the entry looked after the change" vs. "Here's how the entry looks now" was useful, what I often wanted was the kind of diff I would get out of Git: "here's how it looked before the change" vs "here's how it looked after the change".
Maybe our diffs don't store that information, and we would have to reconstruct the entry by replaying commits since a snapshot in order to present the "before" view. So this might be a "big ask". But the "what changed?" model seems to be slightly more useful than the "What did it look like back then, and what does it look like now?" model.
Or that just might be my bias towards the tooling I'm familiar with, where I can easily do git log -1 -p (hash) to see what changed at a point in time. Maybe when I talk to users I'll find that they would prefer to have the feature in its current state, comparing the state after a change to the current state. If so, I'll update the request accordingly.
Who is this feature for?
Users
Pages affected
Activity view
Contributor guide
No contributing guide indexed for this repository
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 with the Activity view named in the issue and trace how its current comparison is represented and where diff history is stored. Done would mean users can compare an entry before and after a change, rather than only comparing the changed state with the current state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100