8000 Question: Different source of API configuration · Issue #123 · cloudcreativity/laravel-json-api · GitHub
[go: up one dir, main page]

Skip to content
Question: Different source of API configuration #123
Closed
@lorenzleutgeb

Description

@lorenzleutgeb

Hi!

I'm using Laravel on top of a custom database architecture. In the database I have all the information needed to generate Adapter, Hydrator, Schema and Validators for all my models. Data is accessible similar using a mechanism similar to Eloquent.

My goal is not to dump auto generated files that can then by picked up by this library but to provide the needed configuration components (listed above) in a programmatic way.

As far as I can see, the only way to configure this library is through configuration files, which are read and transformed in CloudCreativity\LaravelJsonApi\Repository. Given my scenario, I would have to change the implementation of this component, which seems doable but not straight forward (it is referenced in the middleware for looking up the API, the service provider and the resource registrar).

An alternative solution would be to extend this library so that I can provide my own Api object, and register it with the repository. Would you be open to such a change?

It would also be nice to have an interface instead of Api to allow customization.

I am posting here to get a word of advice from you. Have you thought about this use case, and what are your suggested solutions? Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0