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.
27 lines
1.1 KiB
JavaScript
27 lines
1.1 KiB
JavaScript
import Metadata from '../metadata.js';
|
|
/**
|
|
* Pattern that makes it easy to distinguish whether a region has a single
|
|
* international dialing prefix or not. If a region has a single international
|
|
* prefix (e.g. 011 in USA), it will be represented as a string that contains
|
|
* a sequence of ASCII digits, and possibly a tilde, which signals waiting for
|
|
* the tone. If there are multiple available international prefixes in a
|
|
* region, they will be represented as a regex string that always contains one
|
|
* or more characters that are not ASCII digits or a tilde.
|
|
*/
|
|
|
|
var SINGLE_IDD_PREFIX_REG_EXP = /^[\d]+(?:[~\u2053\u223C\uFF5E][\d]+)?$/; // For regions that have multiple IDD prefixes
|
|
// a preferred IDD prefix is returned.
|
|
|
|
export default function getIddPrefix(country, callingCode, metadata) {
|
|
var countryMetadata = new Metadata(metadata);
|
|
countryMetadata.selectNumberingPlan(country, callingCode);
|
|
|
|
if (countryMetadata.defaultIDDPrefix()) {
|
|
return countryMetadata.defaultIDDPrefix();
|
|
}
|
|
|
|
if (SINGLE_IDD_PREFIX_REG_EXP.test(countryMetadata.IDDPrefix())) {
|
|
return countryMetadata.IDDPrefix();
|
|
}
|
|
}
|
|
//# sourceMappingURL=getIddPrefix.js.map
|