Tags give the ability to mark specific points in history as being important
-
v1.1.0
protected1a3ed1db · ·New release v1.1.0: - Enabled changes in traffic allocation during active instruments/experiments - Non-technical fields, schema type, stream, contextual attributes and end date can be edited when the instrument/experiment has already begun collecting data - The number of messages in the Regulation section has been reduced - Fixed a bug that make search not to show results when space character was present - chunks configuration has been restructured/optimized
-
v1.0.6
protectedfd5b38bb · ·New release v1.0.6: - Updated copy of activation confirmation dialog - Improved Regulation section copy - The route for the Read view (when a dot character is present) has been fixed - Deprecated and old contextual/misspelled attributes have been removed/fixed - Updated instrument's sampling configuration section - Added new validation rules that relates selected contextual attributes and risk level
-
v1.0.4
protectedad2ff664 · ·New release v1.0.3: - Fixed some indentation issues - Fixed some readonly fields that were enabled after activating an experiment - Validation suite has been refactored to be more maintainable - Added a specific test cases for the API when format=analytics - Added deactivated experiments to format=analytics response - Some cleanup (typos, unused code/imports, indentation, code style in general, eslint configuration)
-
v1.0.0
protectedd43a9cc3 · ·New release v1.0.0: - Added footer + pagination + search input - Added links to automated analytics - Updated Codex to v2.3.1 - Introduced shared entity store and split pinia stores for instruments and experiments - Fixed some traffic values that exceeded the allowed max traffic - Added future active instruments and experiments to the API responses - Updated sql script according how xLab works and with specific data for testing locally
-
v0.8.4
protected3ba6d3ce · ·New release v0.8.4: - Fixed what xLab shows in the Read view regarding the security legal review when the instrument/experiment is low risk - Added start and end dates in the API responses as `start` and `end` for instruments and experiments (this case only for when mediawiki is the authority) - The the payload of the /api/v1/instruments response has been reduced by removing the non-technical/unneeded fields
-
v0.7.8
protectedd39df8eb · ·New release v0.7.8: Added basic Traffic validation: New validation rules for Traffic section and make some changes related to that component. It's worth noting that some changes have been made for validation to run same way for both client and server sides regarding sample_rate . So far this field was being transformed before sending it to the backend so its structure was different in the client and in the server. But validation must run both sides indistinctly. So that transformation has been delayed to do it in the backend just when preparing data to be saved in the database. That way, sample_rate structure is the same during the validation process (for both client and server) and we transform that field properly before saving it in the database. Now wiki and traffic/sample_rate are validated according to some validation rules that are included in the first AC of T396059 - Inline Server Validation for Wiki: "No wiki has been selected" when the field is empty - Inline Server Validation for Traffic (%): "No traffic assigned" when there is no value in that field - Inline Client Validation for Traffic (%) / Sample Rate: "Enter a value between 0 and 100" or "Enter a value between 0 and 1" depending when registering an experiment or an instrument - Default wiki row has been removed for experiments. By default one row appears but wiki is fully configurable and cannot be removed. For instruments, a default wiki row is still appearing: T396201 - Negative values are now validated properly: T384107 - Add 'performer_is_temp' to contextual attributes table - Limit instruments endpoint to active instruments