Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML Template Improvements #294

Open
1 task
simonharrer opened this issue Jun 25, 2024 · 3 comments
Open
1 task

HTML Template Improvements #294

simonharrer opened this issue Jun 25, 2024 · 3 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@simonharrer
Copy link
Contributor

simonharrer commented Jun 25, 2024

HTML templating needs to be improved.

  • Extension of additional key/value pairs within an already existing element (currently only supported in the info, terms, server block)
  • mark custom fields so we can distinguish between custom fields and standard fields
  • Extension of a whole new top level element that might be nested
  • better design for the servicelevels
  • mobile-friendly html support
  • custom elements can be complex (substructures, arrays, ...)
  • The "Show YAML" should use multi-line syntax for multi-line strings.
@simonharrer simonharrer added the good first issue Good for newcomers label Jun 25, 2024
@simonharrer
Copy link
Contributor Author

Important: the templates are imported in the editor (that is not written in python but in JavaScript). During that process, the templates are transformed a little bit. For any change here, we need to make sure that the editor does not break. https://github.com/datacontract/datacontract-editor

@jochenchrist
Copy link
Contributor

jochenchrist commented Jul 12, 2024

mark custom fields so we can distinguish between custom fields and standard fields

Why?

@simonharrer
Copy link
Contributor Author

mark custom fields so we can distinguish between custom fields and standard fields

Why?

In customer project, when having a lot of extension fields, it might be helpful to see which ones are part of the standard, and which ones are extra fields. But we could postpone this until the desire becomes stronger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants