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

provide public facing API for other gems to use bones functionality #34

Open
banister opened this issue Jul 23, 2012 · 0 comments
Open

Comments

@banister
Copy link

Hi,

I'm building a gem and i'd like to use bones via its ruby API to implement some features. My goal is build a pry-plugin_kit plugin for the Pry REPL. To that end, i'd like the user to be able to type pry --build_plugin my_plugin and it'll use a bones template stored in the gem's directory.

Currently if i want this functionality, i have to get the user to manually copy the bones skeleton to their ~/.mrbones/ directory, right? It woudl be much nicer if i could just tell the bones gem to create a project from a skeleton stored in a directory of my choosing, and nicer still if i could do that without shelling out :P Anyway, let me know what u think.

thanks

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

1 participant