Skip to content
This repository has been archived by the owner on Nov 23, 2023. It is now read-only.

Naming-conventions for configuration names. #15

Open
alexbrasetvik opened this issue Oct 31, 2011 · 1 comment
Open

Naming-conventions for configuration names. #15

alexbrasetvik opened this issue Oct 31, 2011 · 1 comment

Comments

@alexbrasetvik
Copy link
Contributor

Some plugins are configured with "foo_name", while others call them just "bar". Same goes with "_path"-suffixes (pre-dating the !path-concept), "destination" vs "output", etc.

We should clean this up, before we get enough users to warrant dealing with a deprecation phase.

@nkvoll
Copy link
Member

nkvoll commented Nov 4, 2011

I think we should go with "foo" -- less typing and slightly easier on the eyes.

Regarding output_path, however, I'm conflicted -- I guess we rename this to 'output'?

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

No branches or pull requests

2 participants