Skip to content

Track and Display Project Edit History with Diff View #753

Closed

Description

@ReinaMaze

Description: Projects can be edited but there's no audit trail. Implement version history showing all changes with before/after comparisons.

Acceptance Criteria:

Store project versions on edit (max 50 versions)
Version history page: /projects/[id]/history
Version list shows: timestamp, editor, fields changed
Click version to see diff view
Side-by-side or unified diff format
Revert to previous version (owner only)
Version comparison (select 2 versions)
Export version history as JSON
Admin can view history for any project

Activity

  1. rupesh-kumar-sah commented on Oct 17, 2026

    @rupesh-kumar-sah

    Hi maintainers,

    I reviewed "Track and Display Project Edit History with Diff View" and have a structured approach ready for implementation:

    I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.

    I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.

    Thank you!

  2. julietashia9-dev commented on Oct 18, 2026

    @julietashia9-dev

    @julietashia9-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Good day. I would be grateful for the opportunity to be assigned to this issue. Having reviewed the description and acceptance criteria, I understand the objective to be adding an audit trail for project edits in the Dongle frontend. Each edit would store a version, capped at 50 per project, and a history page at /projects/[id]/history would list versions with timestamp, editor, and changed fields, allow side-by-side or unified diffs and comparison of any two versions, support owner-only revert, offer JSON export, and give admins access to any project's history. My intended approach is to first study the existing project edit flow and data model to determine where versions can be captured, then implement version storage with the 50-version limit, the history page and version list, the diff and comparison views, and the revert and export actions with their permission checks. I anticipate having a first version ready within 2 to 3 days given the breadth of the scope, and I will gladly seek the maintainers' guidance in the thread should a question arise regarding where version data should be persisted, how the oldest versions should be pruned once the cap is reached, or the preferred diff library.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @julietashia9-dev to this issue.

  3. Eniola3321 commented on Oct 18, 2026

    @Eniola3321
    Contributor

    @Eniola3321 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    please can i work on the issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Eniola3321 to this issue.

  4. drips-wave commented on Oct 18, 2026

    @drips-wave

    Congratulations, @Eniola3321! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @Eniola3321: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  5. grantfox-oss commented on Oct 20, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @Eniola3321's PR #783 was approved and merged by @ReinaMaze.

    🏆 @Eniola3321: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (815 total points). Track your full progress on GrantFox.

    👏 Great work, @Eniola3321! Keep contributing to HubDApp.

  6. drips-wave commented on Oct 20, 2026

    @drips-wave

    This issue has been completed by @Eniola3321 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Eniola3321: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions