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
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Sgs | T296646 [Epic] Migration of front-end modules to Vue.js components | |||
Resolved | KStoller-WMF | T329033 [Internship] Modernization of web interfaces using Vue.js | |||
Resolved | • VYanez-WMF | T331975 Separate demo components from library components |
Event Timeline
Comment Actions
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.
Comment Actions
The process you are describing is not possible without a build step, are you suggesting to introduce such build step within this task?
Comment Actions
Resolving since we are already hosting the files in separate directories components vs component-demos since 895801