iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build(aio): don't constrain `checkContentRules` to run before another processor (#24000) 

We don't really care when this processor runs as long as it happens
after the tags have been extracted.
By not constraining its `runBefore` property we can ensure that other
processors can be run before it.

PR Close #24000
This commit is contained in:
Pete Bacon Darwin 2018-05-16 17:48:33 +01:00 committed by Miško Hevery
parent 131d0d8e8a
commit 293ec78069
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aio/tools/transforms/angular-base-package/processors/checkContentRules.js vendored
View File

@ -32,7 +32,7 @@ module.exports = function checkContentRules(log, createDocMessage) {
docTypeRules: {},
failOnContentErrors: false,
$runAfter: ['tags-extracted'],
$runBefore: ['processing-docs'],
$runBefore: [],
$process(docs) {
const logMessage = this.failOnContentErrors ? log.error.bind(log) : log.warn.bind(log);
const errors = [];

2
aio/tools/transforms/angular-base-package/processors/checkContentRules.spec.js
View File

@ -18,7 +18,7 @@ describe('checkContentRules processor', function() {
it('shpuld run at the right time', () => {
expect(processor.$runAfter).toEqual(['tags-extracted']);
expect(processor.$runBefore).toEqual(['processing-docs']);
expect(processor.$runBefore).toEqual([]);
});
it('should do nothing if not configured', () => {