You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the Entity and File types are frozen as part of the platformics repo.
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)
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?
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?
The text was updated successfully, but these errors were encountered:
Right now the
Entity
andFile
types are frozen as part of theplatformics
repo.NOTE: Can we use similar solutions for Files?
The text was updated successfully, but these errors were encountered: