Weave Code
Kiota Serialization Text Laravel Package
microsoft/kiota-serialization-text
PHP library for Kiota-generated projects that serializes and deserializes text/plain content types. Add it to your generated API client with Composer: microsoft/kiota-serialization-text.
microsoft/kiota-serialization-text is a PHP serialization library for Kiota-generated clients, enabling seamless serialization and deserialization of text/plain content types. It plugs into the Kiota request pipeline so generated SDKs can read and write plain-text payloads without custom handling.
- Supports serialization to and deserialization from
text/plain - Integrates directly with Kiota-generated PHP projects
- Installs easily via Composer (
composer require microsoft/kiota-serialization-text) - Lightweight, focused implementation with minimal dependencies
- Part of the broader Kiota PHP ecosystem
Frequently asked questions about Kiota Serialization Text
- What is microsoft/kiota-serialization-text used for in a Laravel application?
- It is a Kiota serialization provider that handles text/plain content for PHP clients generated by Kiota. In a Laravel app it is useful only when you already use a Kiota-generated client, such as the Microsoft Graph PHP SDK, and one of the consumed endpoints returns or accepts text/plain. It is not a general HTTP client, a Laravel integration, or a general-purpose text parser.
- How do I install and configure microsoft/kiota-serialization-text in Laravel?
- Install it with Composer using composer require microsoft/kiota-serialization-text, which currently resolves the 2.x line. You then register the text serialization provider in the Kiota request adapter or serialization registry used by your generated client, alongside the JSON and other providers. There is no Laravel service provider or config file to publish because the package is framework-agnostic.
- Does microsoft/kiota-serialization-text support Laravel 10, 11, and 12?
- The package is framework-agnostic, so Laravel compatibility is mostly a PHP version question. The 2.x line requires PHP 8.2 or newer, which fits Laravel 10 on PHP 8.2+ and Laravel 11 or 12 on PHP 8.2 to 8.4. A Laravel 9 or 10 application still on PHP 8.1 is blocked by the PHP floor.
- Do I need microsoft/kiota-serialization-text for the Microsoft Graph PHP SDK in Laravel?
- Only if your generated Graph client handles endpoints that actually use text/plain. Many Graph operations use JSON, which is covered by the JSON serialization provider. If no consumed endpoint returns or accepts text/plain, adding this package is dead weight; if one does, it prevents a missing-provider failure in the Kiota pipeline.
- Can I use microsoft/kiota-serialization-text with Guzzle or Laravel's HTTP client?
- No, it does not integrate with Guzzle, Laravel's HTTP facade, or Saloon. Its scope is implementing Kiota SerializationWriter and ParseNode behavior for text/plain inside Kiota-generated clients. If you call APIs directly with Guzzle or Laravel HTTP, you should handle plain-text responses yourself and do not need this package.
- What PHP versions are required by microsoft/kiota-serialization-text?
- Version 2.x requires PHP 8.2 or newer. The README documents the current 2.0.2 release line. Verify your Laravel platform baseline before adopting it, because an older PHP 8.1 runtime cannot install the current major version.
- Is microsoft/kiota-serialization-text production-ready and actively maintained?
- It is a Microsoft-maintained, MIT-licensed, pure PHP library with a small surface area and visible CI, static analysis, and SonarCloud coverage signals. Direct technical risk is low for its intended use case. The main caution is ecosystem risk: independent adoption is very low, so you may be largely on your own for usage-pattern bugs and examples.
- Why must microsoft/kiota-serialization-text be upgraded in lockstep with Kiota?
- It depends on microsoft/kiota-abstractions, and since Kiota 1.5.0 the core PHP libraries are released in lockstep across the monorepo. That means you cannot safely upgrade this provider independently of the abstractions package and the generated client. Pin compatible versions and include the generated client in upgrade testing.
- How should I test text/plain serialization in a Laravel Kiota client?
- Because the library is pure PHP with no I/O, you can unit test it with a fake ParseNode or SerializationWriter harness. At the application level, add an integration or feature test that feeds a text/plain response through your Kiota-generated client and asserts the resulting string. This is also the best place to catch a missing text serialization provider before production.
- What happens if a Kiota client receives text/plain without this package, and what are the alternatives?
- The likely failure is a runtime serialization error or empty deserialization when the Kiota registry has no provider for text/plain. That is a narrow, late-binding failure that should surface in integration testing rather than silently corrupting data. Alternatives are to add this package, write a custom Kiota SerializationWriter and ParseNode implementation, or avoid Kiota for that call and use Guzzle, Laravel HTTP, or Saloon instead.
Weaver
How can I help you explore Laravel packages today?