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

Associating template files with a target that are not .m or .mm etc #121

Closed
mattyohe opened this issue Mar 19, 2014 · 4 comments · Fixed by #122
Closed

Associating template files with a target that are not .m or .mm etc #121

mattyohe opened this issue Mar 19, 2014 · 4 comments · Fixed by #122

Comments

@mattyohe
Copy link

I have some configuration options in a plist file in my ~/.liftoff/templates directory that I would like associated with the default target. Currently it appears only source files or the Images.xcassets files automatically receive the Target Membership checkmark in the file's identity inspector.

Is there currently a way to associate other files (.plist) with a target?

@gfontenot
Copy link
Member

Can you expand on this use case a little?

@mattyohe
Copy link
Author

Imagine you're producing several apps that each share the same codebase. Rather than taking the route of adding multiple targets to a single project, you've created separate lightweight projects that each depend on a cocoapod that contains this shared codebase. Now to configure each app (colors, crash reporting API keys, urls etc) you place a config.plist in the bundle and associate it with a target. Now this shared codebase simply looks for this config.plist in the main bundle, and references values inside it to use throughout the app, setting colors based on the config etc.

Does this make any more sense?

@mattyohe
Copy link
Author

Honestly, it would make more sense to be able to send in this plist as a configuration parameter along with "Project Name?" rather than in the templates folder, but I haven't looked under the hood of this project yet.

@gfontenot
Copy link
Member

That doesn't make much sense as something to have to enter during every new project, but I can see that users should be able to link in plist files that aren't the Info.plist. I've opened up a PR to solve this issue.

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

Successfully merging a pull request may close this issue.

2 participants