Skip to content

Development environment setup: Events-Backend stubs for Cloud Agent#455

Draft
RavenLLevitt wants to merge 1 commit intomainfrom
cursor/development-environment-setup-9b19
Draft

Development environment setup: Events-Backend stubs for Cloud Agent#455
RavenLLevitt wants to merge 1 commit intomainfrom
cursor/development-environment-setup-9b19

Conversation

@RavenLLevitt
Copy link
Copy Markdown
Collaborator

Summary

Adds stub files for the Events-Backend module so the backend server can start without access to the private Events-Backend repository. This enables Cloud Agent development environments to run the full application stack.

Changes

  • Removes the backend/events symlink (which points to ../../Events-Backend)
  • Adds backend/events/index.js — a minimal Express router stub
  • Adds 12 stub Mongoose schema files in backend/events/schemas/ (rssFeed, approvalFlowDefinition, approvalInstance, event, form, formResponse, eventAnalytics, eventSystemConfig, stakeholderRole, domain, analyticsEvent, eventQR)

Notes

  • The stubs allow the server to start but all events-related API endpoints are non-functional
  • Full events development still requires cloning the actual Events-Backend repo
  • The .gitignore already has backend/events/ listed, but the stubs are force-tracked for Cloud Agent compatibility
  • No other code was modified
Open in Web Open in Cursor 

Replace the Events-Backend symlink with a stub directory containing:
- index.js: Express router (no-op)
- 12 stub Mongoose schemas (rssFeed, approvalFlowDefinition,
  approvalInstance, event, form, formResponse, eventAnalytics,
  eventSystemConfig, stakeholderRole, domain, analyticsEvent, eventQR)

Each schema exports a minimal mongoose.Schema with a name field and
strict: false, allowing the backend server to start without the
private Events-Backend repository.

Co-authored-by: RavenLLevitt <RavenLLevitt@users.noreply.github.com>
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.

2 participants