Structure changes about apple-signin-auth

[NitinHsharma]

Thanks for giving reference of monofile project. I read the topic with a lot of public opinions and before is the mini list of pros and cons

Pros

• Easier to kick start
• faster rollout for the initial phase
• easy to understand the whole logic in a single file by what to do and what not to. (by this you do not need to move from one file to another while going through code in initial stage)
• normally do it for POCs

cons

• Problem in maintaining the code in the long run
• difficult to understand the solution for peers
• changes may cause conflicts in the merge
• Normally do it for maintaining the project for a long time with many contributors

And many more pros and cons.

[nikonhub]

Thank you for giving me credit on it 😂

[a-tokyo]

@NitinHsharma Quite a nice analysis! ( :

So let's close this for now and reopen it once the project scales a bit? thoughts? 🚀

(Feel free to reopen!)

[a-tokyo]

Ooopssss! 😂 Thanks for bringing to my attention, fixed!

Special thanks to the awesome @NitinHsharma 🚀

[a-tokyo]

Hey @NitinHsharma! Thank you so much for your proposal! Really nice notes you got there.

Generally I am a fan of modularization, however, recently Getlify and Dan Abramov brought up a very nice topic about how monofile projects are much easier to manage at the beginning since they focus on the core functionality. They both agreed, and I do as well, that one should start modularizing when one feels the monofile would grow out of hand.

What are your thoughts on this? 🚀

NOTE: Generally I use a similar structure to you mentioned, however I noticed that with this specific project monofile is so much easier to manage. (specially if we decide to move to typescript)

Your input is highly appreciated!