[feature] Implement cascading parameter list

[zuobiao-zhou]

What's changed?

similar to #1976.
relate to #1705

The previous PR caused incorrect parameter display when monitoring the usage of other protocols. This PR fixes this bug.

When add a new monitor using HTTP:

2024-05-13_20-06-51.mp4

When edit a existing monitor using HTTP:

2024-05-13_20-07-15.mp4

Checklist

• I have read the Contributing Guide
• I have written the necessary doc or comment.
• I have added the necessary unit tests and all cases have passed.

Add or update API

• I have added the necessary e2e tests and all cases have passed.

[zuobiao-zhou]

Fixed, thanks. @crossoverJie

[tomsun28]

Hi, thanks for contribution.
I found the cascading paramter rule is parent: [xxx], if the parent is new param like httpMethod, we have to update the webapp code to adapter it. This cannot adapt to the user's dynamic changes, such as adding new parent param but does not modify the front-end code.

How about this rule:

depend:
  - parentField -> value1
  - parentField2 -> value2

eg:

   - field: community
     # name-param field display i18n name
     name:
       zh-CN: SNMP community word
       en-US: SNMP Community
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
     limit: 100
     #required-true or false
     required: false
     # param field input placeholder
     placeholder: 'Snmp community for v1 v2c'
     # dependent parameter values list
     # parent: [ 0,1 ]
     depend:
       - snmpVersion -> 0
       - snmpVersion -> 1

[zuobiao-zhou]

Hi, thanks for contribution. I found the cascading paramter rule is parent: [xxx], if the parent is new param like httpMethod, we have to update the webapp code to adapter it. This cannot adapt to the user's dynamic changes, such as adding new parent param but does not modify the front-end code.

How about this rule:

depend:
  - parentField -> value1
  - parentField2 -> value2

eg:

   - field: community
     # name-param field display i18n name
     name:
       zh-CN: SNMP community word
       en-US: SNMP Community
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
     limit: 100
     #required-true or false
     required: false
     # param field input placeholder
     placeholder: 'Snmp community for v1 v2c'
     # dependent parameter values list
     # parent: [ 0,1 ]
     depend:
       - snmpVersion -> 0
       - snmpVersion -> 1

Got it, I will refactor.

[zuobiao-zhou]

Hi @tomsun28
The new rule is like:

depend:
  snmpVersion:
    - 0
    - 1

BTW, are there any other protocols that require the use of cascading parameters?

[tomsun28]

BTW, are there any other protocols that require the use of cascading parameters?

hi, great job👍, it seem no other params need cascading.

[tomsun28]

👍 LGTM！