chore(doc-gen): add a jquery deploy environment, and give examples one i... #6361
Conversation
|
Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.
If you need to make changes to your pull request, you can update the commit with Thanks again for your help! |
|
Please note that this is pending angular/dgeni-packages#3, a fix for the example processor. |
…e index per environment Adds a jQuery environment, and updates dgeni-packages dependency to add a processor to the docs.angularjs.org package which runs after example index files have been generated. This processor copies the index file once for each deployment environment, adding custom shared scripts described in that env. This does not yet handle changing the target of the iframe, so those all point to the default no matter the version of docs being accessed.
|
The new dgeni-packages version is in - this is ready to go! EDIT: not ready at all - something weird is going on with the index.html generation. EDIT2: Bug addressed in angular/dgeni-packages#5 |
|
Regarding handling retargeting the iframe. This is probably best done by providing a value for the current deployment to angular in the index-xxx.html. The runnableExample directive could then modify the iframe src attribute accordingly. |
| config.set('processing.examples.commonFiles', { | ||
| scripts: [ '../../../angular.js' ], | ||
| stylesheets: [] | ||
| }); | ||
| config.set('processing.examples.dependencyPath', '../../..'); |
There was a problem hiding this comment.
This line needs to be removed as the dependencyPaths are now inside the deployments below.
|
Also we need to change the commit message, which is not in sync with the code now. |
...ndex per environment
Adds a jQuery environment, and adds a processor to the docs.angularjs.org package
which runs after example index files have been generated. This processor copies
the index file once for each deployment environment, adding custom shared scripts
described in that env.
This does not yet handle changing the target of the iframe, so those all point
to the default no matter the version of docs being accessed.