-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Description
The initial implementation of lb4 import-lb3-models can import only models inheriting from models that have a built-in counter-part in LB4: Model, PersistedModel, KeyValueModel.
In this spike, we should research different options for supporting models inheriting from other user-defined models.
There are two major use cases: import a model inheriting from an LB3 built-in model like User and import a model inheriting from an application-specific model.
- How to know where to import the base model from (what path to use in the import statement)? (See also Spike: how to import relations from LB3 models #3812.)
- How to ensure that the base LB3 model has been either already imported to the LB4 app or is part of the import being in progress? (See also Spike: how to import relations from LB3 models #3812.)
- When importing models extending a built-in LB3 model like
User, do we want to preserve this inheritance in LB4 too, or "inline" the LB3 built-in model definition into the target LB4 model?