Weave Code
Onesky Bundle Laravel Package
openclassrooms/onesky-bundle
Symfony bundle for integrating OneSky translation services into PHP applications. It helps manage localization workflows and keep translation files synchronized with OneSky projects, simplifying configuration and exchange of source and translated content in Symfony apps.
One Sky Bundle
Frequently asked questions about Onesky Bundle
- Is openclassrooms/onesky-bundle compatible with Laravel?
- No. It is a Symfony bundle that hooks into the Symfony kernel, DI container, and console commands, and Laravel has no equivalent extension surface. On a Laravel stack you cannot install and use it as designed; at most you can read its OneSky API calls and reimplement them as a first-party service. Build a small adapter around the OneSky REST API using Laravel's HTTP client and an Artisan command instead.
- How do I install openclassrooms/onesky-bundle?
- It is Composer-installable with composer require openclassrooms/onesky-bundle, then registered as a bundle in a Symfony kernel and configured through the Symfony Config component. Before committing, check the composer.json PHP and Symfony version constraints against your matrix, confirm the repo is not archived, and run composer audit. Adoption signals are essentially absent, so verify it installs and passes tests on your supported PHP and Symfony versions first.
- What Laravel versions does this package support?
- None. The package is a Symfony bundle, not a Laravel package, and it does not ship a Laravel service provider, facade, or config file. Any Laravel support would require a fork that replaces the Symfony kernel and DI assumptions with Laravel idioms. Treat the bundle as reference material for OneSky API calls rather than a dependency.
- Can I use it to sync translation files with OneSky in a Laravel app?
- Not directly. The bundle's push and pull logic is wrapped in Symfony console commands and configuration, so you would need to reimplement the OneSky REST calls inside a Laravel command. The underlying interaction is small: pull translated keys into lang/, push newly introduced source keys, and add a diff or dry-run mode so syncs are reviewable. That adapter is usually less work than maintaining a fork of an unmaintained bundle.
- What alternatives exist for integrating OneSky translations into Laravel?
- Check whether OneSky offers an official SDK or a maintained PHP client that the bundle merely wraps, and use that directly if it exists. For Laravel, a thin adapter around the OneSky REST API using Guzzle or Saloon plus an Artisan command is the idiomatic route. For Symfony, use a maintained client as a plain service or register a minimal bundle of your own.
- Is openclassrooms/onesky-bundle maintained?
- Adoption signals are effectively absent: zero stars, zero dependents, and a score of 0, which suggests OpenClassrooms has likely moved on. Before relying on it, check the last commit and release date, whether the repo is archived, and the CI status. Abandonment raises the risk of API drift, unpatchable bugs, and transitive CVEs in an old dependency tree.
- Does openclassrooms/onesky-bundle support PHP 8.2 and 8.3?
- That depends entirely on the composer.json constraints, which you must verify against your supported matrix before committing. The evaluation notes that PHP and Symfony version constraints need checking and that the package may pin an end-of-life HTTP client. Run composer install and the test suite on PHP 8.2 and 8.3 in a throwaway project to confirm.
- How should I handle OneSky API credentials with this bundle?
- Translation-sync tooling routinely handles API keys, so review the bundle's default configuration and logging behavior before putting it near production credentials. Keep keys in environment variables rather than committed config, and confirm request logging does not print auth headers. If you reimplement the client, inject credentials through config and avoid global state so the transport can be mocked in tests.
- How do I test OneSky translation sync without hitting the live API?
- Use an injectable PSR-18 or PSR-7 transport so you can swap in a mock client, and check whether the bundle actually allows this, since hardcoded endpoints or global state would block testing. Write tests for pulling into lang/ or translations/, pushing new keys, and the diff or dry-run path. If the bundle is not injectable, that alone is a reason to write your own small client.
- Should I fork openclassrooms/onesky-bundle for a Laravel project?
- Generally no. A fork turns a dependency into internal code you now own, and the Symfony kernel, DI, and config assumptions are the bulk of the bundle. Since the durable value is the small set of OneSky REST calls, extract those patterns and implement an Artisan command with the Laravel HTTP client instead. Fork only if you need a short-lived reference while migrating.
Weaver
How can I help you explore Laravel packages today?