- How do I install pyaesoneaung/laravel-myanmar-tools in a Laravel app?
- Install it with Composer using composer require pyaesoneaung/laravel-myanmar-tools. The service provider is auto-registered through Laravel package discovery, so no manual registration is normally needed. Publish the config and language files with vendor:publish if you want to adjust defaults; there are no migrations, credentials, or external services involved.
- Which Laravel and PHP versions does this package support?
- Support is defined entirely by the PHP and illuminate/* constraints in the package's composer.json, so read those before requiring it. Because it extends Laravel core primitives such as the validator and Str helpers, it depends on internals that change between majors, so confirm the Laravel versions you need are covered rather than assuming. Once verified, pin an exact version instead of a floating constraint.
- Does it validate Myanmar NRC numbers?
- Yes, NRC format validation is one of the package's core features, exposed as a Laravel validation rule. NRC formats vary by township and by issuance era, so validate against your own corpus of real samples before relying on it in KYC flows. Also make sure failed validation does not log the raw NRC value, since that is national ID data.
- Can I validate and normalize Myanmar phone numbers with it?
- The package provides Myanmar phone number validation and normalization covering the major carrier prefixes such as MPT, Telenor, Ooredoo, and Mytel. Carrier prefix allocation in Myanmar has changed repeatedly, so treat the prefix list as reference data you may need to update. Normalize to a single stored format at the boundary and keep the raw input only if you have a reason to.
- Does the package convert between Zawgyi and Unicode?
- Zawgyi to Unicode transliteration is part of the package's scope and is typically exposed as a string helper or macro. These conversions are notoriously not round-trippable, so pick Unicode as your storage format and convert only at input and display time. Test with real-world text fixtures rather than short sample strings.
- What Myanmar-specific helpers does it offer besides validation rules?
- Beyond validation, the package covers Myanmar addresses, name handling, currency and numeral formatting, and calendar date helpers. The feature inventory is broad and partly macro-based, so confirm exactly which helpers you need exist before designing around them. Anything missing is usually easier to add in your own adapter than to patch upstream.
- How should I test this package before using it in production?
- There is essentially no public production evidence base, so build your own test harness rather than relying on ecosystem adoption. Cover real NRC and phone samples, Zawgyi and Unicode round-trip fixtures, and expected normalized output for each validation rule you use. Assert on your adapter's output, not on package internals, so the tests survive a fork or replacement.
- Is pyaesoneaung/laravel-myanmar-tools safe to use in production?
- It is MIT licensed with no infrastructure requirements, but it has a single maintainer, low star count, and no downstream dependents, which means bus factor one and any defect becomes yours to fix. Isolate every call behind an internal adapter class so the dependency stays a swappable implementation detail. Pin an exact version, and note the future-dated release tag is worth confirming with the maintainer before you depend on it.
- Will its macros collide with other Laravel packages?
- The package extends Laravel by registering macros at boot, which mutates global container state. If another package registers the same macro name on Str, Validator, or a similar class, you get either a boot-time BadMethodCallException or a silent override of behavior. Avoid the problem by never referencing package symbols in domain code and resolving any collision inside a single wrapper class.
- Are there alternatives, or should I write the validation myself?
- The feature surface is small and mostly rule-based, so for a narrow use case writing a handful of custom validation rules and formatters is a realistic option with no third-party risk. If you want existing behavior, evaluate maintained Myanmar locale packages or fork this one under your own namespace. Either way, keep it behind an interface so switching costs a single class.