Another convention?

Hi Dale. The other day we were discussing with Stef that it is common that if you have your repository called XXX then you have the ConfigurationOfXXX class in the package ConfigurationOfXX. In such a case, the #className:  could be also optional if you follow that convention. What I mean is that I would like to do:

 spec project: 'Fuel' with: [
                spec
                    repository: 'http://ss3.gemstone.com/ss/Fuel' ].
       

or

spec project: 'Fuel' with: [
                spec
                    repository: 'http://ss3.gemstone.com/ss/Fuel' .
                    versionString: #'bleedingEdge
]



What do you think?  come on come on! you can do it   ;)

cheers
                   

--
Mariano
http://marianopeck.wordpress.com

Mariano,

that makes a lot of sense ... I'll add a bug report on this ...

Dale

----- Original Message -----
| From: "Mariano Martinez Peck" <[hidden email]>
| To: [hidden email]
| Sent: Friday, December 9, 2011 3:22:07 PM
| Subject: [Metacello] Another convention?
|
| Hi Dale. The other day we were discussing with Stef that it is common
| that if you have your repository called XXX then you have the
| ConfigurationOfXXX class in the package ConfigurationOfXX. In such a
| case, the #className: could be also optional if you follow that
| convention. What I mean is that I would like to do:
|
| spec project: 'Fuel' with: [
| spec
| repository: ' http://ss3.gemstone.com/ss/Fuel ' ].
|
|
| or
|
| spec project: 'Fuel' with: [
| spec
| repository: ' http://ss3.gemstone.com/ss/Fuel ' .
| versionString: #'bleedingEdge
| ]
|
|
|
| What do you think? come on come on! you can do it ;)
|
| cheers
|
|
| --
| Mariano
| http://marianopeck.wordpress.com
|
|

Excellent. Thanks Dale.




--
Mariano
http://marianopeck.wordpress.com