Ignite: Old Ignite folder structure

[mykelaballe]

how can i generate the old Ignite folder structure using ignite new MyAppName? The new boilerplate seems to not include the folders: Actions, Fonts, Utils, Store. Reducers folder is also changed to Redux

[GantMan]

I don't believe we have a boilerplate based on the older structure. I'd be open to listing a fork of the old file layout. Do you want help creating a boilerplate with that structure?

[mykelaballe]

yup that would be great! cause i already have an existing project based on the old folder structure and previous redux logic. i plan to transition everything but not now since im rushing on deploying a new version of my app

[jamonholmgren]

Nice! I'll close for now, but reach out if you need help with your new boilerplate.

[mykelaballe]

where am i gonna grab the fork?

[jamonholmgren]

@mykelaballe I'd start with https://github.com/infinitered/ignite-ir-next, but wait until we release Andross this week (our first major release with Ignite CLI).

[mykelaballe]

ohh too bad. i really need the old structure ASAP

[skellock]

This tag has the 1.0 structure if you need to resurrect some files.

[GantMan]

Yup, look through the releases (https://github.com/infinitered/ignite/releases) and find out when you'd like the old structure, then it's super easy!

[GantMan]

Looks to me like anything before 1.7 should be good: https://github.com/infinitered/ignite/releases/tag/1.7.0

[mykelaballe]

@skellock how should i generate the boilerplate? ill download the repo then call ignite new MyApp inside that repo? also when i looked at the App folder, its still the new folder structure.

@GantMan the same question here, how should i generate it? ill download it and then run command ignite new MyApp, and then it will map my app's name to android's manifest file, gradle, ios AppDelegate file, etc...?

[mykelaballe]

why is it that ignite new MyApp command gets the 1.13.0 folder structure even though the ignite version installed on my windows pc is 1.5.0?

[mykelaballe]

Another thing is that whenever i run the generated boilerplate, i keep getting this error

[GantMan]

run npm dedup

[mykelaballe]

it worked for vector-icons but now another naming collision appeared which is the router-flux. is there an npm dedup recursive command?

[mykelaballe]

[mykelaballe]

i tried deleting the collisioned file stated in the image above, but when i build it again another file has collided with other files again. And it seems to happen repeatedly even though i delete the next files and so on and so forth