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.
35 lines
2.0 KiB
JavaScript
35 lines
2.0 KiB
JavaScript
import { VALID_PUNCTUATION } from '../constants.js'
|
|
|
|
// Removes brackets and replaces dashes with spaces.
|
|
//
|
|
// E.g. "(999) 111-22-33" -> "999 111 22 33"
|
|
//
|
|
// For some reason Google's metadata contains `<intlFormat/>`s with brackets and dashes.
|
|
// Meanwhile, there's no single opinion about using punctuation in international phone numbers.
|
|
//
|
|
// For example, Google's `<intlFormat/>` for USA is `+1 213-373-4253`.
|
|
// And here's a quote from WikiPedia's "North American Numbering Plan" page:
|
|
// https://en.wikipedia.org/wiki/North_American_Numbering_Plan
|
|
//
|
|
// "The country calling code for all countries participating in the NANP is 1.
|
|
// In international format, an NANP number should be listed as +1 301 555 01 00,
|
|
// where 301 is an area code (Maryland)."
|
|
//
|
|
// I personally prefer the international format without any punctuation.
|
|
// For example, brackets are remnants of the old age, meaning that the
|
|
// phone number part in brackets (so called "area code") can be omitted
|
|
// if dialing within the same "area".
|
|
// And hyphens were clearly introduced for splitting local numbers into memorizable groups.
|
|
// For example, remembering "5553535" is difficult but "555-35-35" is much simpler.
|
|
// Imagine a man taking a bus from home to work and seeing an ad with a phone number.
|
|
// He has a couple of seconds to memorize that number until it passes by.
|
|
// If it were spaces instead of hyphens the man wouldn't necessarily get it,
|
|
// but with hyphens instead of spaces the grouping is more explicit.
|
|
// I personally think that hyphens introduce visual clutter,
|
|
// so I prefer replacing them with spaces in international numbers.
|
|
// In the modern age all output is done on displays where spaces are clearly distinguishable
|
|
// so hyphens can be safely replaced with spaces without losing any legibility.
|
|
//
|
|
export default function applyInternationalSeparatorStyle(formattedNumber) {
|
|
return formattedNumber.replace(new RegExp(`[${VALID_PUNCTUATION}]+`, 'g'), ' ').trim()
|
|
} |