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.
protobufjs/ext/descriptor
Experimental extension for interoperability with descriptor.proto types.
Usage
var protobuf = require("protobufjs"), // requires the full library
descriptor = require("protobufjs/ext/descriptor");
var root = ...;
// convert any existing root instance to the corresponding descriptor type
var descriptorMsg = root.toDescriptor("proto2");
// ^ returns a FileDescriptorSet message, see table below
// encode to a descriptor buffer
var buffer = descriptor.FileDescriptorSet.encode(descriptorMsg).finish();
// decode from a descriptor buffer
var decodedDescriptor = descriptor.FileDescriptorSet.decode(buffer);
// convert any existing descriptor to a root instance
root = protobuf.Root.fromDescriptor(decodedDescriptor);
// ^ expects a FileDescriptorSet message or buffer, see table below
// and start all over again
API
The extension adds .fromDescriptor(descriptor[, syntax]) and #toDescriptor([syntax]) methods to reflection objects and exports the .google.protobuf namespace of the internally used Root instance containing the following types present in descriptor.proto:
| Descriptor type | protobuf.js type | Remarks |
|---|---|---|
| FileDescriptorSet | Root | |
| FileDescriptorProto | dependencies are not supported | |
| FileOptions | ||
| FileOptionsOptimizeMode | ||
| SourceCodeInfo | not supported | |
| SourceCodeInfoLocation | ||
| GeneratedCodeInfo | not supported | |
| GeneratedCodeInfoAnnotation | ||
| DescriptorProto | Type | |
| MessageOptions | ||
| DescriptorProtoExtensionRange | ||
| DescriptorProtoReservedRange | ||
| FieldDescriptorProto | Field | |
| FieldDescriptorProtoLabel | ||
| FieldDescriptorProtoType | ||
| FieldOptions | ||
| FieldOptionsCType | ||
| FieldOptionsJSType | ||
| OneofDescriptorProto | OneOf | |
| OneofOptions | ||
| EnumDescriptorProto | Enum | |
| EnumOptions | ||
| EnumValueDescriptorProto | ||
| EnumValueOptions | not supported | |
| ServiceDescriptorProto | Service | |
| ServiceOptions | ||
| MethodDescriptorProto | Method | |
| MethodOptions | ||
| UninterpretedOption | not supported | |
| UninterpretedOptionNamePart |
Note that not all features of descriptor.proto translate perfectly to a protobuf.js root instance. A root instance has only limited knowlege of packages or individual files for example, which is then compensated by guessing and generating fictional file names.
When using TypeScript, the respective interface types can be used to reference specific message instances (i.e. protobuf.Message<IDescriptorProto>).