Document embedder SDK packages only when they are in the same path as the main package.

[isoos]

Running dartdoc on Flutter packages generates docs for the SDK libraries too, and pub site wants to exclude them (pub site issue: dart-lang/pub-dev#2108 ). However using --exclude removes the links, e.g. Future is not linked to the official SDK docs page.

Restricting the embedder SDK to the direct subdirectories solves the issue for the Flutter packages, and also keeps the option to generate embedder SDK docs if needed.

[devoncarew]

@isoos, it looks like there are some travis failures. I think some of that is related to a new version of pedantic. If so, I'll peg to an older version and commit that to master. You'll need to update this branch from master after that.

@keertip for review

[devoncarew]

@isoos, can you update the body of this PR w/ the issues it'll fix?

[devoncarew]

The pedantic change has landed in master.

[keertip]

@isoos, could you rebase and see if the tests pass?

[isoos]

rebased, force pushed

[mit-mit]

@jcollins-g @isoos is anyone looking at fixing this? I'd love to get dart-lang/pub-dev#2117 resolved.

[jcollins-g]

I am not looking at this.

[mit-mit]

Do we have an alternate way of resolving dart-lang/pub-dev#2117 ?

[isoos]

Do we have an alternate way of resolving dart-lang/pub-dev#2117 ?

Note: The package may have changed since last May, but at that time, I tracked the root cause back to the embedder SDK-related code here (and an assumed change in Flutter which was never tracked down when it happened). I have no idea what the embedder SDK-related code is supposed to do or when it is used (or if this is the correct way of resolving the issue), and I can't even say that the PR was the correct way how to address this.

[isoos]

This has been fixed elsewhere.