core/constants/ — Application Constants

To manage Flutter API endpoints and routing paths without magic strings, use a centralized constants file declaring static const strings. This ensures network and UI layers reference immutable values, eliminating duplication and inconsistent route definitions across modules.

The best way to structure Hive storage keys and socket events is grouping them as static constants in a dedicated configuration file. Centralizing these app-level values prevents magic strings, making refactors and testing safe and predictable across your Flutter client.

To add a new backend endpoint, edit your api_constants.dart file and declare the path as a static const string. Use relative paths with {id} placeholders for dynamic segments, ensuring the base URL remains excluded from the constant definition.

Yes, you can use go_router :param syntax inside Flutter route constants. Declaring paths with this notation as static constants ensures consistent navigation and deep linking, allowing UI layers to reference exact routing values without hardcoding strings.

You should not include runtime logic inside Flutter configuration files to maintain deterministic behavior. Keeping constant files limited to static const declarations ensures the application constants remain a single, predictable source of truth during refactoring and testing.