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

Configuration file #68

Open
schultyy opened this issue Sep 22, 2014 · 7 comments
Open

Configuration file #68

schultyy opened this issue Sep 22, 2014 · 7 comments

Comments

@schultyy
Copy link

As already suggested in #67, there should be a project related configuration file.
This file can also define some settings only related to a certain project like:

  • MiniTest related settings like color, different reporter
  • Location of setup file
  • Files which should be checked automatically
@moonglum
Copy link

What format should that be? YAML? Ruby?

@schultyy
Copy link
Author

Yaml is easy to process. JSON would also be fine. I would like to avoid XML ^^

@schultyy
Copy link
Author

I would go for YAML

@moonglum
Copy link

👍 for YAML 😸 Then I vote for the file extension .yaml for that file.

@schultyy
Copy link
Author

agreed :)

On 22 Sep 2014 at 17:12:50, Lucas Dohmen ([email protected]) wrote:

for YAML Then I vote for the file extension .yaml for that file.


Reply to this email directly or view it on GitHub.

@mmmries
Copy link

mmmries commented Oct 6, 2014

After trying out this gem in my gem I think it would be best to put any configuration in the ataru_setup.rb file. You could provide a template when you generate that file and make it work in a very normal ruby way. I'm thinking of something like:

Ataru.configure do |c|
  c.exclude_files = ["docs/future_improvements.md"]
end

require 'minitest-pride'

Just my 2 💶

@moonglum
Copy link

moonglum commented Oct 6, 2014

Yep, that is what we discussed in #75 as well 😄 We should update that here!

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

No branches or pull requests

3 participants