545563e776
- Complete NestJS TypeScript implementation with WebSocket support - Direct messaging (DM) and group chat functionality - End-to-end encryption with AES encryption and key pairs - Media file support (images, videos, audio, documents) up to 100MB - Push notifications with Firebase Cloud Messaging integration - Mention alerts and real-time typing indicators - User authentication with JWT and Passport - SQLite database with TypeORM entities and relationships - Comprehensive API documentation with Swagger/OpenAPI - File upload handling with secure access control - Online/offline status tracking and presence management - Message editing, deletion, and reply functionality - Notification management with automatic cleanup - Health check endpoint for monitoring - CORS configuration for cross-origin requests - Environment-based configuration management - Structured for Flutter SDK integration Features implemented: ✅ Real-time messaging with Socket.IO ✅ User registration and authentication ✅ Direct messages and group chats ✅ Media file uploads and management ✅ End-to-end encryption ✅ Push notifications ✅ Mention alerts ✅ Typing indicators ✅ Message read receipts ✅ Online status tracking ✅ File access control ✅ Comprehensive API documentation Ready for Flutter SDK development and production deployment.
39 lines
1.9 KiB
JavaScript
39 lines
1.9 KiB
JavaScript
"use strict";
|
|
// Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT license.
|
|
// See LICENSE in the project root for license information.
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.Standardization = void 0;
|
|
/**
|
|
* Used to group the {@link StandardTags} definitions according to the level of support
|
|
* expected from documentation tools that implement the standard.
|
|
*/
|
|
var Standardization;
|
|
(function (Standardization) {
|
|
/**
|
|
* TSDoc tags in the "Core" standardization group are considered essential.
|
|
* Their meaning is standardized, and every documentation tool is expected
|
|
* to recognize them. The TSDoc parser library typically provides dedicated APIs
|
|
* for accessing these tags.
|
|
*/
|
|
Standardization["Core"] = "Core";
|
|
/**
|
|
* TSDoc tags in the "Extended" standardization group are optional. Documentation tools
|
|
* may or may not support them. If they do, the syntax and semantics should conform to
|
|
* the TSDoc standard definitions.
|
|
*/
|
|
Standardization["Extended"] = "Extended";
|
|
/**
|
|
* TSDoc tags in the "Discretionary" standardization group are optional. Although the
|
|
* syntax is specified, the semantics for these tags are implementation-specific
|
|
* (and sometimes difficult to describe completely without referring to a specific
|
|
* implementation). Discretionary tags are included in the TSDoc standard to ensure that
|
|
* if two different popular tools use the same tag name, developers can expect the syntax
|
|
* to be the same, and the semantics to be somewhat similar.
|
|
*/
|
|
Standardization["Discretionary"] = "Discretionary";
|
|
/**
|
|
* The tag is not part of the TSDoc standard. All used-defined tags are assigned to this group.
|
|
*/
|
|
Standardization["None"] = "None";
|
|
})(Standardization || (exports.Standardization = Standardization = {}));
|
|
//# sourceMappingURL=Standardization.js.map
|