Skip to content

Have a uniform way when interfacing json files #19

Description

@augustjohansson

Right now there's

  1. set/getJsonStructField
  2. assignStructParams / assignJsonParams
  3. updateJson
    All these have (probably) their pros and cons, but I'd suggests we'll use the set/getJsonStructField, and possibly modify these to handle the cases covered by 2 & 3. Then these can be deleted. Or we simply delete 2 & 3 now and fix errors as they appear.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions