Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor/Rename How-To #50

Open
rodrigo-lima opened this issue Feb 16, 2020 · 4 comments
Open

Refactor/Rename How-To #50

rodrigo-lima opened this issue Feb 16, 2020 · 4 comments

Comments

@rodrigo-lima
Copy link

This is a fantastic starter kit and I thank you all for putting this together for all of us!

Would it be possible to add a "How-To refactor/rename" best practices doc for packages, app name, dependencies, etc. so we're not always using co/touchlab/kampstarter / co.touchlab.kampstarter and we don't break gradle, Xcode, Android builds?

@jmarks213
Copy link

You can refactor the package in the IDE. Edit -> Find -> Replace in path ; Shortcut is crtl + shift + r. You would still need to manually update the file directories to match the new package.

It would be great though if it was possible to generate this project with the details of my own project sans all the helpful docs and images.

@piannaf
Copy link

piannaf commented Apr 24, 2020

Similar ask from recent survey respondent

provide a script to easily rename whole project to add custom branding/package names etc

@coletz
Copy link

coletz commented Sep 16, 2020

I've made a script which seems to work. Tested only on macOS, but should work on linux too (and windows under wsl). It requires "rename", the one from perl.
PS: if you rename the package id using something which starts with "co." (like "co.example.demo") you will get some error message, since the script tries to remove the "co" folder, which is not empty; I should add a check in order to avoid misleading error messages) EDIT: check added
PPS: feel free to copy it or trash it completely

@kpgalligan
Copy link
Contributor

This is kind of old, but we should take a look at the script and discuss this a bit. I just closed another issue that had a similar request (#223). Maybe if this is straightforward we can consider it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants