load.project issues

[krlmlr]

• Use $ to access config options
• Use $ to access my.project.info
• Get default configuration as list
• Redundant code for checking for missing entries in config: Extract to function
• Options that allow on/off should be converted to logical
• Use pattern parameter in dir()
• Vectorize skipping of deprecated files
• Make use of Boolean configuration options
• Use require.package
• Create necessary directories (cf. Optionally, create.project() should create dummy files in empty directories #35)
• warn instead of stopping if configuration file is missing
• Redundant code for loading from cache
• Extract functions, one per step
• allow overriding (some of the) configuration options by (a) new parameter(s)
• warn on extra entries in the configuration
• avoid duplication of global.dcf (Avoid duplication of global.dcf #79)

[krlmlr]

Converted from issue using hub pull-request -i 76. Work in progress.

[krlmlr]

Ready for review.

[KentonWhite]

Can we define deprecated files in an external file. Then as files are deprecated in the future won't need to hunt for them in source code.

[krlmlr]

Are you sure we need it? An external file adds an extra level of complexity, and it might be more difficult to find it. It's only a few files, after all, and the list is not likely to become much larger.

[KentonWhite]

Yeah, it might be a bit of YAGNI, especially if the file list might not change. Perhaps pull it into a function? Can probably be deferred until we need to update the list.

[krlmlr]

Do you think we need 0570eb7 (ad-hoc change of configuration) if we can have multiple config files?

[KentonWhite]

I think it should be kept. One of the annoyances of rails is having to create a new configuration file just to launch with a simple change. I like that this commit can let me override config variables for a quick one off. Multiple config files are then useful for settings I use frequently.

[krlmlr]

Addressed all issues, will merge later today. Thanks for the review.