Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

863 B
Raw Blame

EE Code Structure Notes

Refer to the Backend Module Organization Guide for tips on how to organize EE code.

Naming EE API routes

To make things consistent EE-only API routes should be given /ee/ route names that correspond to their module (i.e., are prefixed with /ee/<module>/). For example, an :subscription-management-only route to delete User subscriptions should be named something like

DELETE /api/ee/subscription-management/user/:id/subscriptions

rather than

DELETE /api/user/:id/subscriptions

Not all EE endpoints follow this pattern yet, but they should; please feel free to fix stuff as you come across it if I don't get to it first.

Questions :interrobang:

Ping me (@camsaul) if you have any questions.