Skip to content

Conversation

@pbrisbin
Copy link
Contributor

See the README.md diff for details.

Also drops exclude_paths support and defaults include_paths to ["./"]
when unspecified (for easier development).

/cc @codeclimate/review @mrb

@mrb
Copy link
Contributor

mrb commented Jan 13, 2016

@pbrisbin Do custom supplied strings get added to the current strings, or do they replace them?

@pbrisbin
Copy link
Contributor Author

The code as it is implements replacement.

@mrb
Copy link
Contributor

mrb commented Jan 13, 2016

@pbrisbin Do you think that's obvious as a consumer of this engine? Could we use a better name to communicate that? Or do we rely on documentation?

@pbrisbin
Copy link
Contributor Author

I (slightly) prefer documentation. If you can think of a better name for the config key, I'm all ears though.

@mrb
Copy link
Contributor

mrb commented Jan 13, 2016

@pbrisbin Ok. With an adjustment to the docs that says "Note: configuration here replaces strings" or whatever, I'm a +1 on this.

Defaulting to `include_paths: [./]` means it's possible to run docker run -v $PWD:/code $image to see raw output from running this engine, which is useful while developing.
@pbrisbin
Copy link
Contributor Author

Ready for another look.

@mrb
Copy link
Contributor

mrb commented Jan 13, 2016

@pbrisbin 👍

pbrisbin added a commit that referenced this pull request Jan 13, 2016
Allow configurability of the FIXME strings
@pbrisbin pbrisbin merged commit 41b7a09 into master Jan 13, 2016
@pbrisbin pbrisbin deleted the pb-config branch January 13, 2016 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants