innobraingmbh/onoffice-structure
Composer 安装命令:
composer require innobraingmbh/onoffice-structure
包简介
Package to extract the enterprise configuration
README 文档
README
Extract and work with the onOffice enterprise field configuration (Modul- und Feldkonfiguration) in Laravel. The package fetches configurations via innobrain/laravel-onoffice-adapter, transforms them into readonly DTOs, and converts them into various output formats using a strategy pattern.
Features
- Fetch field configurations for all onOffice modules (Address, Estate, AgentsLog, Calendar, Email, File, News, Intranet, Project, Task, User)
- Readonly DTOs for Modules, Fields, Permitted Values, Dependencies, and Filters
- Convert to arrays, Laravel validation rules, Prism PHP schemas, or JSON Schema
- Filter fields by configuration-based conditions with a fluent builder
- Sanitize input data against field definitions and permitted values
- Multi-language support (German, English, French, Spanish, Italian, Croatian)
- Extensible converter strategy pattern for custom output formats
Installation
composer require innobraingmbh/onoffice-structure
You can optionally publish the configuration file:
php artisan vendor:publish --provider="Innobrain\Structure\StructureServiceProvider" --tag="onoffice-structure-config"
Usage
Fetching Structure Data
Use the Structure facade or inject Innobrain\Structure\Services\Structure:
use Innobrain\OnOfficeAdapter\Dtos\OnOfficeApiCredentials; use Innobrain\Structure\Enums\FieldConfigurationModule; use Innobrain\Structure\Enums\Language; use Innobrain\Structure\Facades\Structure; $credentials = new OnOfficeApiCredentials('your-token', 'your-secret'); // Fetch all modules (defaults to German labels) $modules = Structure::forClient($credentials)->getModules(); // Fetch specific modules in a specific language $modules = Structure::forClient($credentials)->getModules( only: [FieldConfigurationModule::Address->value, FieldConfigurationModule::Estate->value], language: Language::English, ); // Iterate over modules and fields foreach ($modules as $moduleKey => $module) { echo "Module: {$module->label} ({$module->key->value})\n"; foreach ($module->fields as $fieldKey => $field) { echo " Field: {$field->label} ({$field->key}) - Type: {$field->type->value}\n"; } }
Filtering Fields
Fields can have filter configurations that determine their visibility based on other field values. Use the fluent FieldFilterBuilder to narrow down fields:
$addressModule = $modules->get(FieldConfigurationModule::Address->value); $filteredFields = $addressModule->fields ->whereMatchesFilters() ->where('Art', '2') // only fields visible when Art = 2 ->when($someCondition, fn ($builder) => $builder->where('ArtDaten', '1')) ->get();
Sanitizing Input Data
Remove keys that don't match known fields or have invalid permitted values:
$sanitized = $addressModule->fields->sanitize(collect([ 'Email' => 'test@example.com', 'unknownField' => 'value', // removed: not in field collection 'Beziehung' => '999', // removed: not a permitted value ]));
Converting Data
All DTOs and collections implement Convertible and can be transformed using a ConvertStrategy.
Array Conversion
use Innobrain\Structure\Converters\Array\ArrayConvertStrategy; $strategy = new ArrayConvertStrategy(dropEmpty: true); // remove null/empty values $allModulesArray = $modules->convert($strategy); $moduleArray = $addressModule->convert($strategy); $fieldArray = $addressModule->fields->get('Email')->convert($strategy);
Laravel Validation Rules
use Innobrain\Structure\Converters\LaravelRules\LaravelRulesConvertStrategy; // Pipe-separated strings with nullable (default) $strategy = new LaravelRulesConvertStrategy(pipeSyntax: true, includeNullable: true); $rules = $addressModule->convert($strategy); // ['KdNr' => 'integer|nullable', 'Email' => 'string|max:100|nullable', ...] // Array syntax without nullable $strategy = new LaravelRulesConvertStrategy(pipeSyntax: false, includeNullable: false); $rules = $addressModule->convert($strategy); // ['KdNr' => ['integer'], 'Email' => ['string', 'max:100'], ...] // Multi-select fields automatically get a wildcard rule: // 'Beziehung' => 'array|distinct|nullable', 'Beziehung.*' => 'in:0,1,2,3'
Prism Schema (for AI tooling)
use Innobrain\Structure\Converters\PrismSchema\PrismSchemaConvertStrategy; $strategy = new PrismSchemaConvertStrategy( includeNullable: true, // mark fields without defaults as nullable includeDescriptions: true, // use field labels as descriptions ); $schema = $addressModule->convert($strategy); // Returns an ObjectSchema usable with Prism's structured output
Field type mapping: VarChar/Text/Blob -> StringSchema, Integer/Float -> NumberSchema, Boolean -> BooleanSchema, Date/DateTime -> StringSchema (with format hint), SingleSelect -> EnumSchema, MultiSelect -> ArraySchema<EnumSchema>.
JSON Schema
use Innobrain\Structure\Converters\JsonSchema\JsonSchemaConvertStrategy; $strategy = new JsonSchemaConvertStrategy( includeNullable: true, includeDescriptions: true, ); $schema = $addressModule->convert($strategy); // Returns a JsonSchema ObjectType
Writing a Custom Converter
Implement ConvertStrategy (or extend BaseConvertStrategy) and add convertField, convertModule, etc. methods matching the DTO class names:
use Innobrain\Structure\Converters\Concerns\BaseConvertStrategy; use Innobrain\Structure\Dtos\Field; use Innobrain\Structure\Dtos\Module; final readonly class MyConvertStrategy extends BaseConvertStrategy { public function convertModule(Module $module): mixed { /* ... */ } public function convertField(Field $field): mixed { /* ... */ } } $result = $module->convert(new MyConvertStrategy());
DTOs
All DTOs are readonly and implement Convertible.
| DTO | Key Properties |
|---|---|
Module |
key (FieldConfigurationModule), label, fields (FieldCollection) |
Field |
key, label, type (FieldType), length, permittedValues, default, filters, dependencies, compoundFields, fieldMeasureFormat |
PermittedValue |
key, label |
FieldDependency |
dependentFieldKey, dependentFieldValue |
FieldFilter |
name, config |
Testing
composer test # Run tests composer test-coverage # Run tests with coverage composer analyse # PHPStan static analysis composer format # Rector + Pint formatting
Changelog
Please see CHANGELOG.md for more information on what has changed recently.
Contributing
Contributions are welcome! Please open an issue or pull request. For bug reports, use the Bug Report Template.
Security Vulnerabilities
If you discover a security vulnerability, please send an e-mail to Konstantin Auffinger via the email address in composer.json. All security vulnerabilities will be promptly addressed.
Credits
Built with Spatie's Laravel Package Tools.
License
The MIT License (MIT). Please see composer.json for more information.
innobraingmbh/onoffice-structure 适用场景与选型建议
innobraingmbh/onoffice-structure 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 8.35k 次下载、GitHub Stars 达 0, 最近一次更新时间为 2025 年 05 月 24 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「laravel」 「Innobrain」 「onoffice-structure」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 innobraingmbh/onoffice-structure 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 innobraingmbh/onoffice-structure 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 innobraingmbh/onoffice-structure 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Laravel package to joyfully interact with the onOffice API
Laravel bindings for markitdown.
This is my package laravel-openimmo
This is my package laravel-libpostal
Alfabank REST API integration
Laravel package for Accurate Online API integration.
统计信息
- 总下载量: 8.35k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 3
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2025-05-24