discourse-data-explorer/spec
锦心 760667d744
FIX: Param should be displayed when the default value is invalid (#313)
What's the problem?
===================

TL;DR: When the user enters an incorrect default value, its
corresponding param-input will disappear

When creating a parameter from SQL, we perform cast_to_ruby, which means
that if the default value given by the user is invalid, the entire
parameter will not be added to the param_list of the query.
This behavior is very confusing, and users will not understand why an
incorrect initial value will cause the param-input to disappear.

What's the fix?
================

The cast_to_ruby process is canceled in create_from_sql, so that
param-input with incorrect default value will still be displayed.
We have a simple validation process on the front end, which is enough to
prompt whether some default inputs are incorrect.
2024-08-21 12:03:11 +08:00
..
automation DEV: Rename `Jobs::DiscourseAutomationTracker` -> `Jobs::DiscourseAutomation::Tracker` (#289) 2024-05-06 23:12:48 +03:00
fabricators FEATURE: Allow data explorer query result to be sent as recurring PM (#233) 2023-03-24 16:38:42 +08:00
integration DEV: Fix new Rubocop offenses (#282) 2024-02-29 18:15:57 +01:00
jobs/scheduled DEV: Update linting (#267) 2023-12-01 16:47:54 +01:00
lib FIX: Param should be displayed when the default value is invalid (#313) 2024-08-21 12:03:11 +08:00
requests DEV: Fix new Rubocop offenses (#282) 2024-02-29 18:15:57 +01:00
system UX: Rewrite param-input using FormKit (#307) 2024-08-20 09:42:50 +08:00
tasks DEV: Update plugin to match latest guidelines (#229) 2023-03-22 23:29:08 +02:00
data_explorer_spec.rb DEV: Fix new Rubocop offenses (#282) 2024-02-29 18:15:57 +01:00
guardian_spec.rb DEV: Fix new Rubocop offenses (#282) 2024-02-29 18:15:57 +01:00
report_generator_spec.rb FIX: send single report PM to groups (#284) 2024-03-27 17:40:26 +08:00
result_to_markdown_spec.rb DEV: Fix new Rubocop offenses (#282) 2024-02-29 18:15:57 +01:00