[BUG] startingView not working

[dominiwe]

Environment

Self-Hosted (Docker)

Version

2.0.8

Describe the problem

Setting startingView in the config to minimal doesn't change anything.
Example:

appConfig:
  startingView: minimal

Additional info

I'm using Nginx as a reverse proxy to access the web services running in docker containers.

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[dominiwe]

@Lissy93 Probably closed because I only recently joined GitHub.

[Lissy93]

I'll reopen...

[dominiwe]

I made a typo, see response.

Building and running from source I see this:

Checking config file against schema...

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Warning: 1 issue found in config file
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. /appConfig must NOT have additional properties (startView)

Searching through the source I didn't find the term startView anywhere.

[Lissy93]

That one is caused by a small typo, startView should be startingView ;)

But the original issue is correct, there's a bug in the router, where the config isn't read at time of initialization, causing it to fallback to defaults. I've got a fix ready, and will submit a PR when I get time, this week :)

[liss-bot]

The fix for this issue has now been released in 2.0.9 ✨

If you haven't done so already, please update your instance to 2.0.9 or later. See 2.0.9 for full info.

Feel free to reach out if you need any more support. If you are enjoying Dashy, consider supporting the project.