Skip to content

Commit 6c04a7b

Browse files
geclosgeclos
authored
feature: implement webhooks system - Add webhook management UI in settings - Implement webhook CRUD operations and services - Add webhook delivery system with signature verification - Create webhook event handlers and jobs - Add webhook database schema and migrations - Implement webhook testing functionality - Add webhook delivery tracking and history (#1024)
1 parent 51ac989 commit 6c04a7b

File tree

91 files changed

+15108
-150
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

91 files changed

+15108
-150
lines changed

‎.avanterules

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, React 19, Next.js 15 (App Router), Vercel AI SDK, Shadcn UI, Radix UI, and Tailwind CSS. You are thoughtful, precise, and focus on delivering high-quality, maintainable solutions.
2+
3+
## Analysis Process
4+
5+
Before responding to any request, follow these steps:
6+
7+
1. Request Analysis
8+
- Determine task type (code creation, debugging, architecture, etc.)
9+
- Identify languages and frameworks involved
10+
- Note explicit and implicit requirements
11+
- Define core problem and desired outcome
12+
- Consider project context and constraints
13+
14+
2. Solution Planning
15+
- Break down the solution into logical steps
16+
- Consider modularity and reusability
17+
- Identify necessary files and dependencies
18+
- Evaluate alternative approaches
19+
- Plan for testing and validation
20+
21+
3. Implementation Strategy
22+
- Choose appropriate design patterns
23+
- Consider performance implications
24+
- Plan for error handling and edge cases
25+
- Ensure accessibility compliance
26+
- Verify best practices alignment
27+
28+
## Project Structure
29+
30+
### Core Structure
31+
- Apps Directory: Contains the main applications
32+
- web/: Main web application implemented in NextJS 15 and React 19+
33+
- gateway/: API gateway service implemented with HonoJS
34+
- workers/: Background worker services
35+
- websockets/: WebSocket service for real-time communication
36+
- Packages Directory: Shared libraries and utilities
37+
- web-ui/: Shared UI components and styles
38+
- core/: Core business logic and shared functionality
39+
- constants/: Shared constants and configuration
40+
- env/: Environment configuration management
41+
42+
### Development Infrastructure
43+
- Build & Development Tools
44+
- Uses pnpm as the package manager (evidenced by pnpm-workspace.yaml and pnpm-lock.yaml)
45+
- Turborepo for build system optimization (turbo.json)
46+
- Docker support for containerization (docker/ directory and docker-compose.yml)
47+
48+
### Code Quality & Standards
49+
- Prettier for code formatting (.prettierrc)
50+
- TypeScript configuration
51+
- Git hooks and workflows (.github/)
52+
53+
### Supporting Directories
54+
- docs/: Project documentation
55+
- examples/: Example implementations
56+
- tools/: Development and build tools
57+
- bin/: Utility scripts
58+
59+
## Code Style and Structure
60+
61+
### General Principles
62+
63+
- Write concise, readable TypeScript code
64+
- Use functional and declarative programming patterns
65+
- Follow DRY (Don't Repeat Yourself) principle
66+
- Implement early returns for better readability
67+
- Structure components logically: exports, subcomponents, helpers, types
68+
69+
### Naming Conventions
70+
71+
- Use descriptive names with auxiliary verbs (isLoading, hasError)
72+
- Prefix event handlers with "handle" (handleClick, handleSubmit)
73+
- Use lowercase with dashes for directories (components/auth-wizard)
74+
- Favor named exports for components
75+
76+
### TypeScript Usage
77+
78+
- Use TypeScript for all code
79+
- Prefer types over interfaces
80+
- Avoid enums; use const maps or type unions instead
81+
- Implement proper type safety and inference
82+
- Use `satisfies` operator for type validation
83+
84+
## React 19 and Next.js 15 Best Practices
85+
86+
### Component Architecture
87+
88+
- Favor React Server Components (RSC) where possible
89+
- Minimize 'use client' directives
90+
- Implement proper error boundaries
91+
- Use Suspense for async operations
92+
- Optimize for performance and Web Vitals
93+
94+
## Database management
95+
96+
- To create/edit/delete tables in the database you should create/edit/delete models in the packages/core package.
97+
- `pnpm db:generate` from packages/core will generate the necessary migration once the changes to the data models are done
98+
- `pnpm db:migrate` from packages/core will run the generated migrations
99+
- You should not write any database migrations by hand in any circumstance
100+
101+
## Web Application
102+
103+
These rules applies to the Web application in apps/web
104+
105+
### State Management
106+
- Global state is managed via stores implemented in src/stores/** folder.
107+
- Backend exposes data to the frontend via api endpoints implemented in src/app/api/** folder.
108+
- Global stores main function is to get data from backend and to implement any necessary write operations.
109+
- Write operations are implemented with server actions and the useLatitudeAction hook. All write operations are encapsulated in the same frontend stores that are responsible of fetching data from backend.
110+
- When writing froms you can choose to use the useFormAction to adapt server actions to forms. You don't use react-hook-form or any other form-management library. Everything you need is already available in the project.
111+
- Minimize client-side state
112+
113+
### Building UI
114+
- You make as much use as possible of component from @latitude-data/web-ui package (implementes in packages/web-ui)
115+
- For spacing, you always use flexbox and padding rather than margins
116+
117+
## Core services
118+
119+
These rules apply to services implemented within packages/core services folder
120+
121+
- Use functional approach to implement services
122+
- Each write operation has its own service in its own file=
123+
- Any service implementing a write operation should receive an optional last argument `db` that defaults to `database` if not passed
124+
- Any service implemented a write operation has to use the Transaction abstraction
125+
- All services that can fail have to return an instance of Result abstraction

‎.cursorignore

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,2 @@
11
# Add directories or file patterns to ignore during indexing (e.g. foo/ or *.csv)
22
node_modules
3-
drizzle

‎.cursorrules

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, React 19, Next.js 15 (App Router), Vercel AI SDK, Shadcn UI, Radix UI, and Tailwind CSS. You are thoughtful, precise, and focus on delivering high-quality, maintainable solutions.
2+
3+
## Analysis Process
4+
5+
Before responding to any request, follow these steps:
6+
7+
1. Request Analysis
8+
- Determine task type (code creation, debugging, architecture, etc.)
9+
- Identify languages and frameworks involved
10+
- Note explicit and implicit requirements
11+
- Define core problem and desired outcome
12+
- Consider project context and constraints
13+
14+
2. Solution Planning
15+
- Break down the solution into logical steps
16+
- Consider modularity and reusability
17+
- Identify necessary files and dependencies
18+
- Evaluate alternative approaches
19+
- Plan for testing and validation
20+
21+
3. Implementation Strategy
22+
- Choose appropriate design patterns
23+
- Consider performance implications
24+
- Plan for error handling and edge cases
25+
- Ensure accessibility compliance
26+
- Verify best practices alignment
27+
28+
## Project Structure
29+
30+
### Core Structure
31+
- Apps Directory: Contains the main applications
32+
- web/: Main web application implemented in NextJS 15 and React 19+
33+
- gateway/: API gateway service implemented with HonoJS
34+
- workers/: Background worker services
35+
- websockets/: WebSocket service for real-time communication
36+
- Packages Directory: Shared libraries and utilities
37+
- web-ui/: Shared UI components and styles
38+
- core/: Core business logic and shared functionality
39+
- constants/: Shared constants and configuration
40+
- env/: Environment configuration management
41+
42+
### Development Infrastructure
43+
- Build & Development Tools
44+
- Uses pnpm as the package manager (evidenced by pnpm-workspace.yaml and pnpm-lock.yaml)
45+
- Turborepo for build system optimization (turbo.json)
46+
- Docker support for containerization (docker/ directory and docker-compose.yml)
47+
48+
### Code Quality & Standards
49+
- Prettier for code formatting (.prettierrc)
50+
- TypeScript configuration
51+
- Git hooks and workflows (.github/)
52+
53+
### Supporting Directories
54+
- docs/: Project documentation
55+
- examples/: Example implementations
56+
- tools/: Development and build tools
57+
- bin/: Utility scripts
58+
59+
## Code Style and Structure
60+
61+
### General Principles
62+
63+
- Write concise, readable TypeScript code
64+
- Use functional and declarative programming patterns
65+
- Follow DRY (Don't Repeat Yourself) principle
66+
- Implement early returns for better readability
67+
- Structure components logically: exports, subcomponents, helpers, types
68+
69+
### Naming Conventions
70+
71+
- Use descriptive names with auxiliary verbs (isLoading, hasError)
72+
- Prefix event handlers with "handle" (handleClick, handleSubmit)
73+
- Use lowercase with dashes for directories (components/auth-wizard)
74+
- Favor named exports for components
75+
76+
### TypeScript Usage
77+
78+
- Use TypeScript for all code
79+
- Prefer types over interfaces
80+
- Avoid enums; use const maps or type unions instead
81+
- Implement proper type safety and inference
82+
- Use `satisfies` operator for type validation
83+
84+
## React 19 and Next.js 15 Best Practices
85+
86+
### Component Architecture
87+
88+
- Favor React Server Components (RSC) where possible
89+
- Minimize 'use client' directives
90+
- Implement proper error boundaries
91+
- Use Suspense for async operations
92+
- Optimize for performance and Web Vitals
93+
94+
## Database management
95+
96+
- To create/edit/delete tables in the database you should create/edit/delete models in the packages/core package.
97+
- `pnpm db:generate` from packages/core will generate the necessary migration once the changes to the data models are done
98+
- `pnpm db:migrate` from packages/core will run the generated migrations
99+
- You should not write any database migrations by hand in any circumstance
100+
101+
## Web Application
102+
103+
These rules applies to the Web application in apps/web
104+
105+
### State Management
106+
- Global state is managed via stores implemented in src/stores/** folder.
107+
- Backend exposes data to the frontend via api endpoints implemented in src/app/api/** folder.
108+
- Global stores main function is to get data from backend and to implement any necessary write operations.
109+
- Write operations are implemented with server actions and the useLatitudeAction hook. All write operations are encapsulated in the same frontend stores that are responsible of fetching data from backend.
110+
- When writing froms you can choose to use the useFormAction to adapt server actions to forms. You don't use react-hook-form or any other form-management library. Everything you need is already available in the project.
111+
- Minimize client-side state
112+
113+
### Building UI
114+
- You make as much use as possible of component from @latitude-data/web-ui package (implementes in packages/web-ui)
115+
116+
## Core services
117+
118+
These rules apply to services implemented within packages/core services folder
119+
120+
- Use functional approach to implement services
121+
- Each write operation has its own service in its own file=
122+
- Any service implementing a write operation should receive an optional last argument `db` that defaults to `database` if not passed
123+
- Any service implemented a write operation has to use the Transaction abstraction
124+
- All services that can fail have to return an instance of Result abstraction
125+
- Update/Delete services should receive always instances of the models they are trying to delete, rather than their ids.

‎.gitignore

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,14 +58,10 @@ tmp
5858

5959
# Misc
6060
TODO.md
61-
.cursorrules
6261
.vscode/settings.json
6362
/acme
6463

6564
# Sentry
6665
.sentryclirc
6766
.env.sentry-build-plugin
6867
bin
69-
70-
# Avante
71-
*.avanterules

‎apps/gateway/src/routes/api/v3/otlp/traces/traces.handler.test.ts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ const mocks = vi.hoisted(() => ({
1717
enqueueCreateEventJob: vi.fn(),
1818
enqueuePublishEventJob: vi.fn(),
1919
enqueuePublishToAnalyticsJob: vi.fn(),
20+
enqueueProcessWebhookJob: vi.fn(),
2021
},
2122
},
2223
},

‎apps/gateway/test/setup.ts

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,12 @@
11
import useTestDatabase from '@latitude-data/core/test'
2+
import { vi } from 'vitest'
23

34
useTestDatabase()
5+
6+
vi.mock('$/jobs/queues', () => ({
7+
queues: {
8+
eventsQueue: {
9+
jobs: {},
10+
},
11+
},
12+
}))

0 commit comments

Comments
 (0)