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
{{ message }}
This repository has been archived by the owner on Nov 3, 2020. It is now read-only.
I think we need to distinguish between installing your first cocoapod env (someone completely new to using CP), updating your current env, and wanting to start with a clean slate and doing a fresh install (overwrite current env). The last is probably not high on the feature requirement list, but I will include it for completeness.
(1) New user - first time install / experience
=> prompt installation.
Already covered here, and as far as I can see implemented and done ✅. Yay!
(2) CP user - first time install / experience
=> prompt update / no prompt if not required
A CP user is defined by already having an CP environment. This can either be updated (great way to nudge for that), or be left alone.
Sample idea:
With the confirmation prompt along the lines of:
"You already have a tool installed. This will update your existing configuration. / This will update Cocoapods to the latest and greatest. "
"If you need to keep your current installation, this will overwrite it. You may want to choose an alternate filename or directory. "
"Cancel | Update"
(3) CP / App user, wanting to start from scratch
=> a "fresh install" button somewhere
I know I've definitely been in this situation when I started developing. If, one day, there would be preferences, or otherwise a small button somewhere. Like previously mentioned though, this is very much at the bottom of the feature list.
Dev work required (probably) (I should dig around the code more!)
detecting current environment
detecting versioning / the need for CP CLI update
the actual updating of the env (but I'm assuming this is the same as the overwrite)
Assets
update copy (for banner, help, prompt)
Thoughts?
The text was updated successfully, but these errors were encountered:
I think we need to distinguish between installing your first cocoapod env (someone completely new to using CP), updating your current env, and wanting to start with a clean slate and doing a fresh install (overwrite current env). The last is probably not high on the feature requirement list, but I will include it for completeness.
(1) New user - first time install / experience
=> prompt installation.
Already covered here, and as far as I can see implemented and done ✅. Yay!
(2) CP user - first time install / experience
=> prompt update / no prompt if not required
A CP user is defined by already having an CP environment. This can either be updated (great way to nudge for that), or be left alone.
Sample idea:
With the confirmation prompt along the lines of:
"You already have a tool installed. This will update your existing configuration. / This will update Cocoapods to the latest and greatest. "
"If you need to keep your current installation, this will overwrite it. You may want to choose an alternate filename or directory. "
"Cancel | Update"
(3) CP / App user, wanting to start from scratch
=> a "fresh install" button somewhere
I know I've definitely been in this situation when I started developing. If, one day, there would be preferences, or otherwise a small button somewhere. Like previously mentioned though, this is very much at the bottom of the feature list.
Dev work required (probably) (I should dig around the code more!)
Assets
Thoughts?
The text was updated successfully, but these errors were encountered: