legend-studio
legend-studio copied to clipboard
Feature: Support for sub-typing handling
Right now we do keep track of subtypes and supertypes in the graph, but for a lot of our checks, we don't handle covariance and contravariance properly.
- [ ] Covariant for union operation class mapping type scanning (e.g.
Worker
extendsPerson
, so if the target class for the op class mapping isPerson
, any class mapping forWorker
should be listed as well) - [ ] Expected type label in the lambda editor now does not check for subtype, only strict type equivalent.
As we discussed, we should also support:
- [ ] Add support for mapping subtypes in mapping editor UI
- [ ] Enhance the mapping algorithm to take care of subtypes. e.g. Mark parent class as mapped if either subtype is mapped in the query build's explorer tree
We should do this post https://github.com/finos/legend-studio/issues/1070