We need to come up with a migration plan so that we don't get stuck in a situation where there is a bug / feature gap in our dependency that can't be fixed.
This is the high level issue to trigger brainstorming; we'll probably break it into separate issues / HLDs.
Decision points include:
fast-foundation component base classes are going away
fast-foundation utilities are going away
fast-element legacy branch is receiving very little attention in favor of their vNext branch
🧹 Tech Debt
Various FAST packages that we depend on are going away or changing their mission: https://github.com/microsoft/fast/issues/6955
We need to come up with a migration plan so that we don't get stuck in a situation where there is a bug / feature gap in our dependency that can't be fixed.
This is the high level issue to trigger brainstorming; we'll probably break it into separate issues / HLDs.
Decision points include:
fast-foundation
component base classes are going awayfast-foundation
utilities are going awayfast-element
legacy branch is receiving very little attention in favor of their vNext branch