Hi Gianluca, For me I try to use /assets to imply and assert files that participate in the asset-pipeline and are compiled & handled in a particular way with its own build system entirely separate from Angular
-Andrew On Fri, Apr 18, 2025 at 8:54 AM Gianluca Sartori <g.sart...@gmail.com> wrote: > Hi Andrew, > > out of curiosity, what's the reason why you are not using the > `/grails-app/assets` folder to store your client side JS code? > > Gianluca Sartori > > On Fri, 18 Apr 2025 at 14:44, Andrew Garcia <and...@goodshuffle.com > .invalid> > wrote: > > > Hi Gianluca, > > We hold out angular files in src/main/client which I’d say also makes it > > qualify as the “webapp”. For me the grails-app folder helps make clear > the > > separation of concerns; grails-app is my backend benefiting from all the > > frameworks benefits and conventions, src is the Wild West of plain Java > > classes (usually global enums) and a place for modern front end > frameworks > > to live. > > > > -Andrew > > > > Sent from my iPhone > > > > > On Apr 18, 2025, at 7:23 AM, Søren Berg Glasius <soe...@glasius.dk> > > wrote: > > > > > > Hi Gianluca, > > > > > > To me, grails-app is just a folder name like webapp, so I don't see the > > > benefit of changing the folder-name, except for a few letters shorter. > > > > > > If others think the idea is good, I'm not opposed to it, I just don't > > see a > > > big win. > > > > > >> Den fre. 18. apr. 2025 kl. 11.01 skrev Gianluca Sartori < > > g.sart...@gmail.com > > >>> : > > >> > > >> I've been thinking about this forever... > > >> > > >> We have the `grails-app` folder containing the conventions over > > >> configuration project structure that is a Grails standard, a different > > one > > >> from the `src` folder structure. > > >> > > >> The fact it contains `grails` in its name can be useful to immediately > > >> recognise the type of the project by giving a quick look at the > > directory > > >> tree. But to my eyes that is all it does. > > >> > > >> I think today I finally found the braveness and recklessness to > propose > > we > > >> change it to a more "domain specific" or "technical" name instead of > > having > > >> the name of the product in it. > > >> > > >> The meaning of that folder should be given by its role in the context > > >> rather than a marketing/communication purpose. > > >> > > >> So I am proposing we change the `grails-app` to `webapp` to indicate > it > > >> contains the web part of the application. > > >> > > >> Pros: > > >> - Removes the name of the product from a technical folder > > >> - Gives it a meaning that is immediately intelligible from a developer > > >> point of view (more people know what a `webapp` is that a > `grails-app`, > > no > > >> need to explain further) > > >> - It is a good time to make this change since the move to Apache is a > > big > > >> change/event > > >> > > >> Cons: > > >> - Breaking change when porting applications from older Grails versions > > >> (must be documented but it's an easy fix) > > >> > > >> Bomb dropped, what is the community opinion? > > >> > > >> Cheers, > > >> Gianluca Sartori > > >> > > > > > > > > > -- > > > > > > Med venlig hilsen, > > > Søren Berg Glasius > > > > > > Hedevej 1, Gl. Rye, 8680 Ry > > > Mobile: +45 40 44 91 88 > > > --- Press ESC once to quit - twice to save the changes. > > > -- *Andrew Garcia* | Co-Founder & CEO and...@goodshuffle.com *Goodshuffle Pro* <https://pro.goodshuffle.com/?utm_source=goodshuffle&utm_medium=email&utm_campaign=employeesignature&fbid=emailsignaturehomepage> | Read our reviews on Capterra <https://www.capterra.com/p/167364/Goodshuffle-Pro/reviews/> <https://www.facebook.com/Goodshuffle/> <https://www.instagram.com/goodshuffle/> <https://www.linkedin.com/company/goodshuffle/posts/?feedView=all> <https://www.youtube.com/c/GoodshufflePro> <https://pro.goodshuffle.com/dispatch-lp?utm_source=goodshuffle&utm_medium=referral&utm_campaign=Feature_Release>
