Tags give the ability to mark specific points in history as being important
-
v0.6.9
21a4ba3f · ·New release v0.6.9: - Updated Name form component - Fixed margin for the main error message
-
v0.6.8
6715d2bb · ·New release v0.6.8: - Fix start + end dates with UTC noon time in database - Replaced skipWhen with omitWhen to omit validation rules - Minor fixes to forms
-
-
v0.6.6
cde96ac1 · ·New release v0.6.6: - Added better validation to forms - Expand domains in /api/v1/experiments?authority=varnish response - Update CI config
-
v0.6.5
35896a32 · ·New release v0.6.5: - Added better validation to forms - Expand domains in /api/v1/experiments?authority=varnish response - Update CI config
-
-
-
v0.6.2
a57e2440 · ·Version 0.6.2: - Invalidate api routes not explicitly specified - Update analytics + base experiments endpoint
-
v0.6.1
9c236e11 · ·New release v0.6.1: - Backend refactored as ES modules - Sample rate has been update to percentages - Fixed query for analytics config API response
-
v0.6.0
5f936cf9 · ·- npm package security updates - Add query parameters to experiments endpoint - .env file updates - Add lodash as dependency
-
v0.5.8
b1677353 · ·Address Design Review feedback points 1, 2, 3, 4, and 9 from https://phabricator.wikimedia.org/T390036#10748263, namely: - For some reason, I can't make the tooltip that clarifies the meaning of the "Split" indicators to be displayed. Would it be possible to trigger it when the split span is hovered? - [Control] The suggested copy for the Control group's description was: "The control group represents users who receive the existing experience. It serves as the benchmark for measuring the impact of the changes being tested.". Does this proposal sound good? - Variation module: To avoid redundancy, the "Machine-readable name" and "Description" sections don't need to be included in the Variantion module. The corresponding fields will already display this information. - Variation module: Thanks for incorporating the clever machine-readable placeholder suggestion! It works amazing. I would just recommend that we also only display the "e.g.," bit when users enter a value in the "Variation name" field. I think this would avoid any potential temporary confusion. Does that sound good? - Since they are purely decorative (unlike the ones included in interactive elements), would it be possible to apply a lighter color (color-subtle) to the user-avatar icons?
-
v0.5.6
24466ffd · ·New release v0.5.6: - Migrate from features to variations: Switch from features (AKA feature variants) - pairs of names and boolean values - to variations/groups. Variations can have: - A name (required) - A machine-readable name, which is the sluggified name (required) - A description (optional) -
v0.5.5
2cbd5522 · ·New release v0.5.5: - Fixed the alignment for human and machine-readable name - Added a workaround to use feature name as groups
-
-
v0.5.3
06c29834 · ·New release v0.5.3: - Update requirements for EPIC - Fix wrong base stream names - Fix multiselect lookup readonly functionality - Minor fixes
-
-
-
v0.5.0
7a377968 · ·New release v0.5.0: - T374957: MPIC: Update A/B test and instrument forms with new Sampling fields - T377811 MPIC: UI Layout design - same width for all pages - removed mediawiki.product_metrics.mint_for_readers from MPIC mock data we use for unit testing - Change copy according to spreadsheet - T377315: MPIC: Improve copy of risk acknowledgement checkbox - T373907: MPIC: Improve application copy - Follow-up on copy fix updates - T374979: MPIC: Update app header - human name field is shown again - T377826: MPIC: UI improvements for the catalog table - T381997: MPIC: make acceptance checkbox required - Fixed the way we transform wikis and sample size - T380282: MenuButton: Prevent menus from displaying selected state by default - Centered the login box horizontally and vertically - Added a label to notify users that okrs and teams are optional fields - T381801: MPIC: Consistently represent dates/times internally - T381614: [MPIC] Dates shift from the selected days after experiment is launched
-
v0.4.1
9f657ddf · ·New release v0.4.1: - Fixed how progress is shown for experiments in the read view
-
v0.4.0
d4b915dd · ·New release v0.4.0: - Set tooltip for variants fields when A/B test is already activated - T379247: MPIC: Set form fields as read-only where appropriate when editing an instrument/experiments - Remove "Start from template" option: - T381309: MPIC: Remove "What would you like to do" section from forms - Duration form improvements: start and end date instead amount time and description - T377816: MPIC: Duration form group improvements - Determine how contextual attributes should be populated. - T366951: MPIC: Determine how contextual attributes should be populated - T377353: MPIC: Error thrown if optional description field is left empty - T380230: MPIC: Replace cdxIconAlert by new Power icon in actions menu - Set font weight as bold for titles in the Read view - T381319: [MPIC] Variable Titles on Intrument / Experiment page no longer bold - Update MPIC API response for variants: - T375906: Simplify ExperimentManager API - New flag to save when an instrument/experiment was activated for the first time: - T379247: MPIC: Set form fields as read-only where appropriate when editing an instrument/experiments - T379355: MPIC: Register the fact that an instrument/experiment has been activated for the first time - Fixed wrong style for some labels that were configured as description instead: - T377558: MPIC: Correct typographic styles