stubs and atoum extensions

[agallou]

Some extensions add new asserters.

Do you know how we could also add autocomplete on this asserters ?

(adding another atoum class causes problems for the autocompletion).

(
plus, if we found there could be packaging questions, where do we put the stub ?

• atoum/stub : won't have implementation problems, but, autocomplete will show unavailable methods
• atoum/blackfire-extension
• atoum/blackfire-extension-stubs
  )
  (in the last 2, I don't know how we could do this).

[jubianchi]

@agallou I would say that each extension should expose its own stubs. I'll try to build one for an extension to see how we could make this.

[agallou]

Proposal :

• stubs are defined in the extension (file1 and file2)
• in the stubs repository, we use each extension trait (file3)

Example : https://gist.github.com/agallou/1bde12b1f3bea9894b0a

This means we have to maintain a list of extensions in the asserters.php file of the stubs projets (it won't cause any problem if the trait does not exists).
I'm not a fan of this but haven't found another way to do this.

[Grummfy]

+1 for me

[Grummfy]

well let's see atoum/atoum#753