Skip to content

feat: implement attestation and usage read endpoints with row-level authorization - #69

Open
ayo-ola0710 wants to merge 4 commits into
FinesseStudioLab:mainfrom
ayo-ola0710:query-and-list-endpoints
Open

feat: implement attestation and usage read endpoints with row-level authorization#69
ayo-ola0710 wants to merge 4 commits into
FinesseStudioLab:mainfrom
ayo-ola0710:query-and-list-endpoints

Conversation

@ayo-ola0710

Copy link
Copy Markdown

What this changes

I introduced the core read API endpoints (/v1/attestations and /v1/usage) required to serve dashboard exports and verification flows. To support these endpoints, we configured Prisma ORM using a local SQLite adapter and defined schemas for both attestations and usage. The service layer logic is now firmly secured with strict row-level authorization—ensuring callers can only fetch data scoped to their tenant identity—and includes stable cursor pagination designed to handle continuously growing datasets without skipping rows. Finally, we tied this together with comprehensive Zod query validation, added robust integration tests to prevent cross-tenant data leaks, and updated our .gitignore to prevent committing local development databases.

Close #56

Why

How it was verified

  • [. ] Existing tests pass
  • [ .] New tests cover the change
  • No change to a public contract interface, or a migration note is included

Risk

@joelpeace48-cell

Copy link
Copy Markdown
Contributor

@ayo-ola0710, Ci fails, ensure all ci passes and also resolve conflicts

@ayo-ola0710

Copy link
Copy Markdown
Author

@joelpeace48-cell

Pls review again

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

routes: query and list endpoints for attestations and usage

2 participants