Skip to content

Generator: Alternative data sources  #2

@kstrohmayer

Description

@kstrohmayer

Actually, the data used for the template generation is provided via one json file only. Based on actual use cases the following improvements are proposed.

  //marker_template_start
  //data: fc.json
  //template: apb_slv_mux_module_body.j2
  //marker_template_code
  • Allow more than one json file as data source (list of json file is possible). Should be look like this
  //marker_template_start
  //data: [fc.json, project.jason, test.jason]
  //template: apb_slv_mux_module_body.j2
  //marker_template_code
  • Allow an inline json object definition
  //marker_template_start
  //data: "{"ports": [0, 1], "addr_base": ["4'h01", "4'h02"]}"
  //template: apb_slv_mux_module_body.j2
  //marker_template_code
  • A combination of both options should be possible.
  //marker_template_start
  //data: ["{"ports": [0, 1], "addr_base": ["4'h01", "4'h02"]}", fc.json]
  //template: apb_slv_mux_module_body.j2
  //marker_template_code

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions