Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Fixes #222
The Problem
Options only get added by Components when
addComponentis called. ForDefaultTheme, it was only being added in theRendererinsideprepareTheme. However, when you tried to set a theme option (e.g.gaID), the option declaration has not been added yet to theOptionsbag. WhenApplication.bootstrapis called, which in turn callsOptions.setValue, the declarations don't exist yet so Typedoc fails.The Fix
Move
DefaultThemeoptions toRendererbecauseRendereris added immediately in theApplicationconstructor.There may be a cleaner way to fix this without moving the options if we can initialize the theme before app bootstrap is called or if the decorator just registered options itself (the main issue there is that the order of the Component and Options decorator execution is in a way such that
_componentNameis not set before the Options decorator factory runs, so it'sundefined). You might be able to use the reflection helpers to find the parent Component (class context) of the Options property decorator.