7031ea4f7b
* Clean up our component types * Clamp our Rule Schedule inputs to safe values * If the user enters a value > Number.MAX_SAFE_INTEGER, it will be updated to Number.MAX_SAFE_INTEGER * If the user enters non-numeric text, it will be updated to 0 * Ensure that we do not go below the default value 0 is not necessarily a reasonable default, but we already have a variable for the default value. * Update cypress interaction with schedule fields Now that we set defaults for bad values, it's no longer possible to "clear" the numeric input. However, to get roughly the same behavior we can instead select the current value and start typing. |
||
|---|---|---|
| .. | ||
| actions | ||
| alerts | ||
| apm | ||
| audit_trail | ||
| beats_management | ||
| canvas | ||
| case | ||
| cloud | ||
| code | ||
| console_extensions | ||
| cross_cluster_replication | ||
| dashboard_enhanced | ||
| dashboard_mode | ||
| data_enhanced | ||
| discover_enhanced | ||
| drilldowns/url_drilldown | ||
| embeddable_enhanced | ||
| encrypted_saved_objects | ||
| enterprise_search | ||
| event_log | ||
| features | ||
| file_upload | ||
| global_search | ||
| global_search_bar | ||
| global_search_providers | ||
| graph | ||
| grokdebugger | ||
| index_lifecycle_management | ||
| index_management | ||
| infra | ||
| ingest_manager | ||
| ingest_pipelines | ||
| lens | ||
| license_management | ||
| licensing | ||
| lists | ||
| logstash | ||
| maps | ||
| maps_legacy_licensing | ||
| ml | ||
| monitoring | ||
| observability | ||
| painless_lab | ||
| remote_clusters | ||
| reporting | ||
| rollup | ||
| searchprofiler | ||
| security | ||
| security_solution | ||
| snapshot_restore | ||
| spaces | ||
| stack_alerts | ||
| task_manager | ||
| telemetry_collection_xpack | ||
| transform | ||
| translations | ||
| triggers_actions_ui | ||
| ui_actions_enhanced | ||
| upgrade_assistant | ||
| uptime | ||
| watcher | ||
| xpack_legacy | ||