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

SPIKE: Can we auto-generate base (e.g Entity) code? #26

Open
jgadling opened this issue May 13, 2024 · 0 comments
Open

SPIKE: Can we auto-generate base (e.g Entity) code? #26

jgadling opened this issue May 13, 2024 · 0 comments
Assignees

Comments

@jgadling
Copy link
Contributor

jgadling commented May 13, 2024

Right now the Entity and File types are frozen as part of the platformics repo.

  1. There are probably use cases where other applications need to add different base columns to base classes. Can we define a minimum base set of fields for a base Entity class and allow extra fields to be added in the schema? (this means codegen'ing the Entity types, probably)
  2. Can codegen dynamically understand whether File is being used, and en/disable any File functionality from appearing in the GQL frontend if it's not used?
  3. LinkML supports multiple base classes - for example we can have a BaseBook class that's extended by a FanatasyNovel class. SQLAlchemy and GraphQL support this pattern fine as well. Can we also support it in Platformics?

NOTE: Can we use similar solutions for Files?

@jgadling jgadling self-assigned this Jul 11, 2024
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

1 participant