Global Branching Limitation with TypeScript v2 Functions

Ask the Community
1

We’re trying to use Global Branching to make an end-to-end change across Ontology, Functions, and Workshop, but we’re hitting a limitation with TypeScript v2 functions.

Scenario

  • We add a new property in the Ontology within a branch

  • We can successfully use it in pipelines and Workshop in that branch

Issue

Our functions are built using TypeScript v2, and:

  • We can’t edit or version function code within the branch

  • The function compiler only sees the main schema

  • So we can’t reference the new property added in the branch

Impact

This breaks the end-to-end workflow:

  • Ontology, pipelines, and Workshop are branch-aware :white_check_mark:

  • TypeScript v2 functions behave as versioned artifacts :cross_mark:

Questions

  • What’s the recommended approach to handle this?

  • Are there best practices for coordinating ontology changes with v2 functions?

  • Are there plans to make TypeScript v2 repos compatible with Global Branching?

Would appreciate insights from others who have faced this.