Advanced_view does not work with JSON arrays

[sedubois]

Currently it is not possible to use the advanced_view option for displaying JSON arrays as the code is defined as follows:

      def advanced_view?
        advanced_view.present? && advanced_view.is_a?(Hash)
      end

E.g if the JSON value is ["one", "two", "three"], it would be nice to be able to just display one, two, three instead of the heavy-looking jsoneditor, and also this advanced_view is necessary to enforce the structure of the data (e.g ensuring the editor won't enter a hash when an array should be provided).

[volkov-sergey]

Hey @sedubois nice catch, thanks. What do you think will be the most comfortable way to use an array feature?

Something like this:

Field::JSONB.with_options(array: true)

or

Field::JSONB.with_options(advanced_view: [])

Share your opinion, please

[sedubois]

@volkov-sergey at first thought I would use another name than "advanced view", technically what is being described here is a description of the JSON's schema. E.g for both arrays and objects:

# JSON array
Field::JSONB.with_options(schema: Field::JSONB::Array(
  Field::String
))
# JSON object
Field::JSONB.with_options(schema: Field::JSONB::Hash(
  'name'  => Field::String,
  ...
))

Or something like that.

Then there is the (separate) question of how to render the form and data, either with jsoneditor or custom. To start, could just use custom views when schema is provided (like now). Then as a second step there could be a way to control this too (either by passing a render option, or by letting user override views).

[volkov-sergey]

@sedubois working on it

[uysimatpassbase]

How is it going for this feature?