fix(code-explorer): resolving starting path when not available #376
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 an issue with the code-explorer dying when it couldn't resolve to child directories within the
examplePath.For example, when trying to start fetching the contents for
examples/react/pagination/src, where the leaf/srcdirectory did not exist, the whole application would simply fail.To fix this, the contents will always be fetched from the contents API from the base of the
examplePath(i.e.examples/react/pagination). From there on, once the contents have been fetched, the logic indetermineStartingFilePathwill resolve it to the correct starting file-path to have correct file opened in the explorer.This results in a UI change, where the contents of the file-tree will differ from the existing implementation.
Important
The default opened/"starting file" will remain the same for users.
Old:

New:
