We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be good if you could outsource the configuration sections to separate files:
The main configuration file could then look like this:
pageInfo: title: <title> appConfig: defaultOpeningMethod: modal hideComponents: hideHeading: true hideNav: true hideSettings: true hideFooter: true enableMultiTasking: true disableConfiguration: true disableUpdateChecks: true sections: - name: Favorites icon: star.svg items: - title: <Service_1> url: https://service_1 target: workspace - [...] {{- $file := glob "/config/*.yml" }} {{- fileContent | toYaml | expandenv | nindent 2 }} {{- end }}
An example file called example_section.yml could then have the following content:
example_section.yml
- name: Example section items: - title: <Service_X> url: https://service_x - [...]
Medium (Would be very useful)
None
The text was updated successfully, but these errors were encountered:
Lissy93
No branches or pull requests
Is your feature request related to a problem? If so, please describe.
It would be good if you could outsource the configuration sections to separate files:
Describe the solution you'd like
The main configuration file could then look like this:
An example file called
example_section.yml
could then have the following content:Priority
Medium (Would be very useful)
Is this something you would be keen to implement
None
The text was updated successfully, but these errors were encountered: