Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple build-in schema #10

Open
metaodi opened this issue Sep 18, 2021 · 3 comments
Open

Decouple build-in schema #10

metaodi opened this issue Sep 18, 2021 · 3 comments

Comments

@metaodi
Copy link
Owner

metaodi commented Sep 18, 2021

  • provide current schema as "plugin" of sorts
  • Standard schema should contain only standard fields (?)
  • maybe provide a default mapping per module (?)
  • test with different instances
@mokko
Copy link

mokko commented Sep 26, 2021

Let me know if you want to test in our instance. [email protected]. Or if I should test it for you.

@metaodi
Copy link
Owner Author

metaodi commented Sep 28, 2021

@mokko thanks for the kind offer. I currently have an instance I can use to test. But I will get back to you, once I figured out a better way to handle the schema. It's still a bit messy in my code 😄

@metaodi
Copy link
Owner Author

metaodi commented Sep 28, 2021

Note to myself: map_function is not a suitable way to handle the schema on a client level. Depending on the requested object, the desired schema changes.

I guess the library should return a sensible default schema for all modules and have a separate mechanism to change the schema based on the requested module (?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants