Skip to content

CSV/JSON export of the current services dashboard view with safe escaping #631

Closed as not planned

Description

@mikewheeleer

Summary

Users can't get services dashboard data out of the app. Add a client-side export of the currently-filtered view as CSV and JSON with correct escaping (including formula-injection safety).

Why this matters

Export is table stakes for a data tool, and naive CSV is a formula-injection risk. Correct escaping makes it safe and useful.

Requirements

  • Export the currently-filtered services dashboard as CSV and JSON.
  • Escape correctly: quotes, commas, newlines, and leading = + - @ (CSV formula-injection).
  • Respect the active filters/sort; export what the user sees.
  • Trigger a client download; accessible control.

Technical guidance

  • Neutralize formula-triggering leading characters in CSV cells.
  • Stream/generate without blocking the UI for large views.

Edge cases — each must have a test

  • export respects the active filter
  • cells with commas/quotes/newlines -> valid CSV
  • cell starting with = -> neutralized
  • empty view -> valid empty export
  • JSON export round-trips

Acceptance criteria

  • All requirements and every edge case above implemented and covered by tests
  • New unit and integration tests; existing tests still pass and no regressions
  • Structured, typed errors (no leaked internals; stable codes)
  • npm run lint, npm test, and npm run build all pass locally
  • Code follows the repo's existing conventions; no duplication or dead code
  • Short docs/comments explaining the design and any non-obvious decisions
  • PR description explains the approach and includes Closes #<issue>

Out of scope

  • Server-side/large-dataset export
  • XLSX format

Rewards

Part of the GrantFox OSS / Official Campaign (FWC26) — this task may be rewarded. PR quality is assessed by AI: depth, correctness under edge cases, meaningful tests, and clean design are what earn the reward. Shallow changes (typos, formatting, trivial docs) do not qualify.

Activity

  1. guptakumarranjeet150 commented on Sep 9, 2026

    @guptakumarranjeet150

    Hi everyone,

    I would like to resolve this issue. Here is my proposed execution plan:

    • Implementation: Build CSV/JSON export of the current services dashboard view with safe escaping with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
    • Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
    • Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

    I am ready to start immediately—please assign this to me!

  2. ranjeet150 commented on Sep 13, 2026

    @ranjeet150

    Hi maintainers,

    I would like to resolve this issue. Here is my proposed execution plan:

    • Implementation: Build CSV/JSON export of the current services dashboard view with safe escaping with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
    • Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
    • Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

    Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

  3. Rodrigoue9 commented on Oct 1, 2026

    @Rodrigoue9

    Hi team! I'd love to take on #631 (CSV/JSON export of the current services dashboard view with safe escaping).

    Technical Analysis & Implementation Approach

    1. Architectural Scope & Affected Modules:
      • Clean, modular implementation strictly following the existing project structure and conventions.
      • Isolated boundaries ensuring zero regressions on adjacent services.
    2. State Management & Core Logic:
      • Directly addressing key acceptance criteria:
        • All requirements and every edge case above implemented and covered by tests
        • New unit and integration tests; existing tests still pass and no regressions
        • Structured, typed errors (no leaked internals; stable codes)
        • npm run lint, npm test, and npm run build all pass locally
    3. API & Boundary Resilience:
      • Defensive error handling, clean teardown/unmount lifecycle, and typed interfaces.

    Verification & Testing Strategy

    • Comprehensive unit and integration test coverage targeting the acceptance criteria, edge cases, and error recovery.
    • Verification of clean build, strict TypeScript types, and zero regressions across the existing test suite.
    • Production Track Record: Verified merged PRs in cybermax4200/stellar-did-credit #898 & #900 (+400 points Wave 9), approved review in documenso/documenso #3275, merged PRs in Astrea-Payouts/astrea #251, #214, #213, and Bitcoindefi/OpenAO #218.

    Ready for instant push and PR as soon as officially assigned! Looking forward to delivering.

  4. woahwhattheheck commented on Oct 6, 2026

    @woahwhattheheck

    /claim #631

    #645

  5. mikewheeleer commented on Oct 18, 2026

    @mikewheeleer
    ContributorAuthor

    Closing as part of a repository reset; a fresh set of issues will be opened shortly.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions