Type aliasing

[deanmarcussen]

We have some types (WorkflowType, and Workflow), which are fixed as being in an Orchard Core assembly.

We want to migrate away from those types, to a custom type, as we are outgrowing the Orchard workflows engine, and need to support additional properties.

Currently I think the only way to do this is to migrate the Type column to a new value, which with +100 tenants, we'd rather not.

Would you (or is there already) support a type aliasing mechanism, or event that we could hook into to create an alias for specific types, mapping them to a new Type name?

[sebastienros]

If we are talking about type name representations, yes. Ideally with a model driven approach, and a custom attribute that can be placed on types too. Also please look at how STJ is doing it, AFAIR it was good.

[deanmarcussen]

so just to clarify this is not completely for Json conversion, but the Type string in the Document table use for sql queries.

ITypeService (replacable, but ...)

for this kind of line

_queryState._sqlBuilder.Parameters["@Type"] = _session.Store.TypeNames[typeof(T)];

I see you have this attribute already

var customName = typeInfo.GetCustomAttribute<SimplifiedTypeNameAttribute>();

but in our case, that woud require applying the attribute to a class we don't control (OC's classes)

[sebastienros]

Yes, not the JSON document. Needs an indirection for external types, agreed. Configuration is preferred.