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

Support app namespace module #47

Open
msakrejda opened this issue Jul 2, 2014 · 5 comments
Open

Support app namespace module #47

msakrejda opened this issue Jul 2, 2014 · 5 comments

Comments

@msakrejda
Copy link
Contributor

I decided that I wanted my app code namespaced in a module, but the pliny generator commands don't support this. I end up wrapping things in module Foo ... end manually, and I inevitably miss something and things break. Could the generator support this out of the box, perhaps optionally?

@brandur
Copy link
Member

brandur commented Jul 3, 2014

@deafbybeheading It seems like maybe another flag to remember might be a little difficult to discover, and not too much less error prone than manually having to remember to edit by hand. What do you think?

I wonder if we could start to support something like .pliny.yaml that just remembers things like your preferred endpoint namespace and such.

@msakrejda
Copy link
Contributor Author

@brandur that could definitely work. I agree that having a flag every time is not a great implementation.

@brandur
Copy link
Member

brandur commented Jul 3, 2014

Cool, +1.

@pedro @tmaier Any thoughts on the possibility of a .pliny.yaml? Not sure if it's overkill, but it might be a useful addition.

@tmaier
Copy link
Member

tmaier commented Jul 3, 2014

Could we name it .interagent.yml and save everything related to prmd, heroics etc?

Something like https://github.com/interagent/pliny/blob/master/lib/pliny/tasks/schema.rake should be then obsolete

@brandur
Copy link
Member

brandur commented Jul 3, 2014

@tmaier +1, thanks!

I think we have some higher priority stuff to get in, but let's keep this one on the back burner.

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

3 participants