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
Templates for the v4 model are currently hard-coded in tooling and also don't match the official v2 schema. They are using a schema I'll call v1.1, which was a temporary workaround to get these working before the v2 schema was finalized. The v1.1 schema was something I came up with and the goal was to minimize the changes from v1 while still fully supporting the new model templates at parity with the old model. By comparison, the v2 schema is way different than the v1 schema so moving to that schema (once it was finalized) was more complicated.
Templates for the v4 model are currently hard-coded in tooling and also don't match the official v2 schema. They are using a schema I'll call v1.1, which was a temporary workaround to get these working before the v2 schema was finalized. The v1.1 schema was something I came up with and the goal was to minimize the changes from v1 while still fully supporting the new model templates at parity with the old model. By comparison, the v2 schema is way different than the v1 schema so moving to that schema (once it was finalized) was more complicated.
v1.1 schema
Hard-coded location of v1.1 schema templates:
Here is the custom logic to support the v1.1 schema (just as an fyi):
v2 schema
I worked on updating templates to the v2 schema, but we abandoned the effort after we decided we weren't going to support the portal.
The text was updated successfully, but these errors were encountered: