Automated Action 545563e776 Implement comprehensive real-time chat API with NestJS
- 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.
2025-06-21 17:13:05 +00:00

8.4 KiB

file-entry-cache - Changelog

v6.0.1

v6.0.0

v5.0.1

  • Bug Fixes
    • Fix missing checksum comparison from reconcile since now we use mtime and size by default. - e858aa9, [Roy Riojas](https://github.com/Roy Riojas), 04/02/2019 09:30:22

      Old mode using checkSum can still be used by passing the useCheckSum parameter to the create or createFromFile methods.

v5.0.0

  • Refactoring
    • Make checksum comparison optional - b0f9ae0, [Roy Riojas](https://github.com/Roy Riojas), 03/02/2019 18:17:39

      To determine if a file has changed we were using the checksum in the newer versions, but eslint was relying on the old behavior where we use the mtime and file size to determine if a file changed. That's why we decided to make the checksum check optional.

      To use it:

      // to make the cache use the checkSum check do the following:
      var fCache = fileEntryCache.create(cacheName, dir, useCheckSum); // pass the third parameter as true
      var otherCache = fileEntryCache.createFromFile(cacheName, useCheckSum); // pass the second parameter as true
      

v4.0.0

  • Build Scripts Changes

  • Other changes

    • Remove object-assign dependency. - d0f598e, [Corey Farrell](https://github.com/Corey Farrell), 08/01/2019 20:09:51

      node.js >=4 is required so object-assign is no longer needed, the native Object.assign can be used instead.

v3.0.0

v2.0.0

v1.3.1

v1.3.0

v1.2.4

  • Enhancements

v1.2.3

  • Build Scripts Changes

v1.2.2

  • Build Scripts Changes
    • Add changelogx section to package.json - a3916ff, royriojas, 11/09/2015 16:00:26

v1.2.1

  • Build Scripts Changes

  • Other changes

    • Update dependencies Replaced lodash.assign with smaller object-assign Fixed tests for windows - 0ad3000, [Bogdan Chadkin](https://github.com/Bogdan Chadkin), 11/09/2015 15:44:18

v1.2.0

  • Features
    • analyzeFiles now returns also the files that were removed - 6ac2431, royriojas, 04/09/2015 12:40:53

v1.1.1

v1.1.0