You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@fbrnc Good Idea. Maybe a composer.json also? But where to store these files. Obviously I cannot put them in the extension folder (Namespace/Module). Maybe put them in the same folder as the uninstall script and the file containing all the generated file names? I'm open for ideas
Well, composer.json can only be a dummy file that would require some more manual editing since the module doesn't know anything about your composer namespace. But it being there will motivate more people to start thinking about it :)
Both files composer.json and modman might only make sense in the root directory of the download folder. I wouldn't expect them to show up anywhere if you chose to directly install the module while generating (which btw, didn't work for me. But I didn't mind since I prefer it to generate a package anyways :)
Along with creating all project files it would be great is a modman file was generated.
The text was updated successfully, but these errors were encountered: