Page MenuHomePhabricator

Separate demo components from library components
Closed, ResolvedPublic

Description

It would be nice to have a distinct folder for the components that GrowthExperiments extension will use as a compiled library as opposed of the components that are only used in the documentation. eg: components

Event Timeline

To clarify, the idea is that there is a components directory that is used by both the MediaWiki code (e.g. code that is in modules/ext.growthExperiments.StructuredTask.PreEdit/{SomeFiles}.vue) and in the demo directory (documentation/frontend/component-demos).

Both the MediaWiki extension code and the demo directory will need to import from the same shared component library.

To clarify, the idea is that there is a components directory that is used by both the MediaWiki code (e.g. code that is in modules/ext.growthExperiments.StructuredTask.PreEdit/{SomeFiles}.vue) and in the demo directory (documentation/frontend/component-demos).

Both the MediaWiki extension code and the demo directory will need to import from the same shared component library.

The process you are describing is not possible without a build step, are you suggesting to introduce such build step within this task?

To clarify, the idea is that there is a components directory that is used by both the MediaWiki code (e.g. code that is in modules/ext.growthExperiments.StructuredTask.PreEdit/{SomeFiles}.vue) and in the demo directory (documentation/frontend/component-demos).

Both the MediaWiki extension code and the demo directory will need to import from the same shared component library.

The process you are describing is not possible without a build step, are you suggesting to introduce such build step within this task?

I think eventually we will need that, yes.

Sgs changed the task status from Open to In Progress.May 15 2023, 10:09 AM

Resolving since we are already hosting the files in separate directories components vs component-demos since 895801