I think, the contribution is happening on the renderer side and not on main side. Hence you see undefined.

Yes, I forgot that contributions are only required from the renderer side.

For my specific fix, I split my contributions into two: configuration (down in platform) and others (up in workbench).

But it took me way too long to figure this one out. I just wasn't expecting the config service not to have defaults. It would be great to have warnings when accessing unset configuration values, for which no default was ever specified. Renaming the issue.

One way to do is while accessing the value, check if the requested setting is registered or not. Obviously this should be done only in dev mode to not impact perf. But one problem is that at present, there are quite number of such unregistered settings that components are accessing. Hence, I think it is not worth doing this.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!