Events out of order

[danguilherme]

I'm writing a DocPad plugin, and I'm finding some trouble in the order of the events. They do not seem to work as the DocPad website states:

Available Events
Sorted by their flow of execution within DocPad

• extendTemplateData
• extendCollections
• ...

In my plugin, if I put simple console.logs in these functions, the output is:

> extendCollections called
> extendTemplateData called

It gets worse if I declare the collections property in my DocPad configuration:

docpadConfig:
    collections:
        posts:
            console.log('collections.posts called');
            // I'd like to access the collection created by my plugin

It is called before any of the above events, so the collection I created on extendCollections isn't available. Am I doing something wrong? Shouldn't I have access to collections "extended" in extendCollections?

[balupton]

thanks for feedback!

seems the docs are incorrect:

docpad/src/lib/docpad.coffee

Lines 2442 to 2446 in e5e9846

	postTasks.addTask 'extend collections', (complete) ->
	docpad.extendCollections(complete)
	postTasks.addTask 'fetch plugins templateData', (complete) ->
	docpad.emitSerial('extendTemplateData', {templateData:docpad.pluginsTemplateData}, complete)

It is called before any of the above events, so the collection I created on extendCollections isn't available. Am I doing something wrong? Shouldn't I have access to collections "extended" in extendCollections?

extendCollections is for injecting new collections, populateCollections is for adding documents for them, there isn't currently something in between