<FromGitter>
<damianham> When scaffolding out a resource I used name of 'Path' which was fine in crystal v0.27 but is a new struct in v0.28 so I had a name clash for the model. The upshot is I have had to rename the resource. Not a big problem as it is early days in the life of this app. I probably shouldn't have used such a common name for a resource. Would it be useful to suffix generated models with 'Model' as we do with controllers
<FromGitter>
... so there is no possibility of a name clash with a future version of crystal ?
<waheedi>
FromGitter: Good story :), well, I think adding 'Model' to each model resource would be a big change. I think the naming needs to be better described/defined. As Path used in this example is really simple, yet it can mean many different things.
<FromGitter>
<rmarronnier> Hey all, do any of you has an idea when amber 0.28 would be released? Days / weeks? I'm relying on the heroku amber build pack which relies on crystal 0.28
<FromGitter>
<rmarronnier> @damianham Maybe a check against a list of protected names would be enough ? Crystal syntax will eventually settle down :-)