7 Mar
2011
7 Mar
'11
5:26 p.m.
On Mar 7, 2011, at 9:32 AM, Simon Denier wrote:
I am in the process (that is, when my mind is not full
with the 1000 things to do when moving to a new city) of refactoring package blueprints,
with multiple objectives in mind:
- make package blueprints work with namespaces
- a testbed for Chef queries
- rewriting the code to make it a bit more object-oriented
- add tests
There is one loophole I would like to expose and get your opinion about. Package
blueprints shows references between classes across packages. Unfortunately nothing has
been planned to handle class extensions. Right now there are just ignored so the picture
given by package blueprints might be incomplete (but not false).
I don't plan for now to do something about this but if some people want to give a
thought about this and later add their idea, they are welcome.
indeed. we ignore them because a reference made in an extension does not really belongs to
the package class but
package extension.
Stef