Inly\Core\Support\....
Use this section for reusable APIs that do one thing well, such as validating or normalizing input, mapping package-specific data, or exposing a focused helper around a well-defined domain concept.
What Belongs Here
Support APIs usually have these traits:- They solve a narrow problem with a small public API.
- They are reusable across documents, actions, services, jobs, and app code.
- They do not wrap an external HTTP service.
- They do not need container registration to be useful.
- They are often safe to use as plain PHP value helpers.
How This Differs From Other Reference Sections
Use these sections consistently:- Support APIs for focused helpers in
Inly\Core\Support\.... - Services for package services with broader runtime responsibilities, configuration, or infrastructure concerns.
- SDKs for integrations that wrap third-party APIs.
- Internals for framework-level helpers and package behavior that support the platform itself.
If you are naming a new package helper, prefer adding it under
Inly\Core\Support\... and documenting it here when it exposes a reusable public API.Available Support APIs
Swedish Bank Account
Parse, validate, normalize, and derive bank metadata for Swedish domestic bank account numbers.
Writing Guidelines
When you document a Support API, describe:- The domain problem it solves.
- The public entry points developers should call first.
- The return values or exceptions they should expect.
- Any normalization rules or edge cases that affect downstream integrations.
- At least one realistic package use case.
Next Steps
- Read the
Swedish Bank Accountreference for a concrete example of this category.