Tags give the ability to mark specific points in history as being important
-
v0.7.1
protected7228c6b7 · ·New release v0.7.1: - Follow up dates validation - Update experiment/instrument start/end time to 14:30 UTC - Fixed additional padding for icons
-
v0.7.0
protected826ef040 · ·New release v0.7.0: - Added instructions to update canonical-data submodule before running xLab - Form validation fixes - Added validation for dates
-
v0.6.9
protected21a4ba3f · ·New release v0.6.9: - Updated Name form component - Fixed margin for the main error message
-
v0.6.8
protected6715d2bb · ·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
protectedcde96ac1 · ·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
protected35896a32 · ·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
protecteda57e2440 · ·Version 0.6.2: - Invalidate api routes not explicitly specified - Update analytics + base experiments endpoint
-
v0.6.1
protected9c236e11 · ·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
protected5f936cf9 · ·- npm package security updates - Add query parameters to experiments endpoint - .env file updates - Add lodash as dependency
-
v0.5.8
protectedb1677353 · ·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
protected24466ffd · ·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)