Multi version by HerrTopi · Pull Request #2396 · instructure/instructure-ui

HerrTopi · 2026-02-04T08:49:28Z

No description provided.

ToMESSKa

How would the folder structure look in like a component like Select? It's a bit different from Metric in a way it has additonal layer of folders e.g.:

src/
├── Metric/ 
└── MetricGroup/

src/
└── Select/ 
    ├── Group/
    ├── Option/
    └── index.tsx

Like this:

src/
├── Select/
│   ├── 11_5/
│   └── 11_6/
├── Group/
│   ├── 11_5/
│   └── 11_6/
├── Option/
│   ├── 11_5/
│   └── 11_6/
└── exports/
    ├── 11_5.ts 
    └── 11_6.ts

Or like this?

src/
├── Select/
│   ├── 11_5/
│   │   ├── Group/
│   │   └── Option/
│   └── 11_6/
│       ├── Group/
│       └── Option/
└── exports/
    ├── 11_5.ts  
    └── 11_6.ts

Or something else?

HerrTopi · 2026-02-04T16:27:01Z

How would the folder structure look in like a component like Select? It's a bit different from Metric in a way it has additonal layer of folders e.g.:

src/
├── Metric/ 
└── MetricGroup/

src/
└── Select/ 
    ├── Group/
    ├── Option/
    └── index.tsx

Like this:

src/
├── Select/
│   ├── 11_5/
│   └── 11_6/
├── Group/
│   ├── 11_5/
│   └── 11_6/
├── Option/
│   ├── 11_5/
│   └── 11_6/
└── exports/
    ├── 11_5.ts 
    └── 11_6.ts

Or like this?

src/
├── Select/
│   ├── 11_5/
│   │   ├── Group/
│   │   └── Option/
│   └── 11_6/
│       ├── Group/
│       └── Option/
└── exports/
    ├── 11_5.ts  
    └── 11_6.ts

Or something else?

Very good catch! I think it depends. If Group and Option is a standalone component, then the first version, if not (e.g.: it's only a subcomponent of Select), the secont version.

… not include functional components

For now it only parses V1 components. It also does not parse components that use the new structure and there are several CSS errors

…ort (now withStyleLegacy)

github-actions · 2026-02-23T16:28:04Z

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-02-27 14:35 UTC

HerrTopi · 2026-02-23T19:22:16Z

cypress/webpack.config.cjs

        if (pkgName && pkgName.startsWith('@instructure/')) {
-          // Alias package name to its source directory
-          aliases[pkgName] = pkgPath
+          // Alias subpath exports (e.g., './latest', './v11_6') to source files.


All the changes in this file are AI generated. They "work" but not double checked by human

ToMESSKa

After comparing the local multi-version against https://instructure.design/ I noticed the components above use the v12 design for some reason.

Another problem might be that some of the components virtually look the same so you cannot tell if a component uses the v11 design or v12 design by simply just looking at them. So there might be a component using v12 but looking like a v11 component.

ToMESSKa · 2026-02-24T10:52:03Z