UI: Hide connector inputs labelled as hidden

[sherifnada]

Tell us about the problem you're trying to solve

#5465 is a good example of us needing to define some parameters that are used only for development or testing but which are not visible to the user. It would be nice to be able to define those in the spec for very clear visibility, but this is not a

Describe the solution you’d like

I would like a connector to be able to label its spec inputs as hidden:true and have the UI hide them e.g:

{
  connectionSpecification: {
     properties: {
       p1: {
         type: string
         hidden: true
       }
     }
  }
}

[jamakase]

@sherifnada I understand why you may need it, however, I believe that it is actually not what should be handled on frontend side. Hiding the field actually means, that you want to totally remove this field ( don't validate it, don't display it ) and all of its descendants in case of the object. If it's going to be used for testing purposes only ( in dev only? ) it is not a problem to change spec and update connector.

Isn't it better to traverse the schema and return the proper schema to be displayed from the server? In this case, any other client that will use our API won't need to adjust the logic and know, that field with hidden is actually skipped field even if it's added into required section

[jamakase]

@jrhizor Actually this is already supported with airbyte_hidden tag that was introduced to support proper oauth behaviour.

[sherifnada]

@jamakase is this then considered "official"/defined behavior? Should we add it to the spec reference?

[jamakase]

Not sure what you mean as official defined behaviour. We just do not display fields with airbyte_hidden :)