| { | |
| "$schema": "https://aka.ms/codetour-schema", | |
| "title": "Relatient - Endpoint creation", | |
| "steps": [ | |
| { | |
| "file": "packages/rest-typings/src/v1/omnichannel.ts", | |
| "description": "Welcome!\n\nLet's assume you want to create a new Omnichannel Endpoint.\n\nFirst thing: this is the \"rest typings\" package, here we add all endpoint typings. This file is specific for omnichannel endpoints, so we'll start here", | |
| "line": 2718, | |
| "selection": { | |
| "start": { |
| Rocket.Chat folder structure | |
| This is a non-extensive documentation about the current Rocket.Chat file structure (19/05). Alongside a brief description of the folder , there's one (or more) pair of , containing a high level categorization for the folder: - [Important] means something can be a service by itself - [Important][-servicename-] means that something can be part of a defined service - [Settings/Integrations/Types/Utils] means that the folder can be moved to the appropiate folder - [FrontEnd] means a folder's are only (or almost all related) to front end. The treatment for these folders should be done by the FE team. | |
| . | |
| ├── app | |
| The `app` folder contains "services" used by FE & BE. Each package is "isolated" from the others, and they store logic inside client/server folders (according to use) | |
| A "service" can hold just FE/BE functionallity depending on the structure it has. This was the standard when starting to use meteor, but it's now deprecated. | |
| Since a refactor to this folder can take a l |
/server folder/app folder (this looks like the meteor standard for packages)