Simplified config editing system

[cmdcolin]

This is not a fully fleshed out idea, but I think it would be nice to have a simpler way of accessing renderer config slots in the config json

There could possibly be snapshot preprocessors or something to help pass these values along

Example of idea: a "renderer" config slot with a "color" key. This would make it easier for people to change color. More examples would be valuable perhaps, but I think the color example is useful to think about, just making it easier for someone to modify their track color

{
      "type": "VariantTrack",
      "trackId": "variant_colors",
      "name": "variant colors",
      "category": ["VCF"],
      "assemblyNames": ["volvox"],
      "adapter": {
        "type": "VcfTabixAdapter",
        "vcfGzLocation": {
          "uri": "volvox.filtered.vcf.gz"
        },
        "index": {
          "location": {
            "uri": "volvox.filtered.vcf.gz.tbi"
          }
        }
      },
      "renderer": { "color":"purple"}
    }

from pairing with @rbuels

[Averstic]

+1, This would be very useful to have!

[cmdcolin]

@Averstic thanks for adding interest...will try to keep this in mind

[carolinebridge]

As per discussion in meeting:

• might be relevant to an entire config simplification effort
• could do something with pre-processing snapshots where we can do something like "does this file end with .bam, guess the adapter slot and fill it in"
• something like: {"name": "mybam", "url": "myfile.bam" }
• improve experience with using embedded tools so the user doesn't need to have a comprehensive understanding of track config

could do:

• simplified config schema that gets converted to old schema
• or just simplify the entire schema uniformly

...possibly more benefit to simplifying the config we already have with some pre-processing

[carolinebridge]

"auto-zod" for error handling / validating snapshots