KevLehman

/* eslint-disable no-console */
const ARRAY_SIZE = parseInt(process.env.ARRAY_SIZE || "2_000_000", 10);
const WARMUP_RUNS = 1;
const MEASURE_RUNS = 3;

function formatBytes(bytes) {
  if (bytes < 1024) return `${bytes} B`;
  const units = ["KB", "MB", "GB", "TB"];
  let i = -1;
  let value = bytes;

KevLehman

const data = require('./2mfKxOI9iPDobZFHAXL7uMgyg9i.json')

function getExecDiffInSecs(start, end) {
	return (new Date(end) - new Date(start)) / 1000 / 60;
}

function printOverallExecTime() {
	const total = getExecDiffInSecs(data.execution.startTime, data.execution.endTime);

	console.log(`TOTAL TIME: ${total}m`);

KevLehman

{
  "$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": {

KevLehman

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

KevLehman

RC Arch

1. App is a monorepo containing FE & BE

• App is made with Meteor
• API and server information can be found at /server folder
• There's also "common" (server code) at /app folder (this looks like the meteor standard for packages)
• Packaging was using Meteor packages but now normal import/requires can be used. This is much better

/app

• This folder encapsulates packages (like a Pluggabble structure)