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

Read configuration file #1

Closed
rmrhz opened this issue Jul 27, 2016 · 10 comments
Closed

Read configuration file #1

rmrhz opened this issue Jul 27, 2016 · 10 comments

Comments

@rmrhz
Copy link
Contributor

rmrhz commented Jul 27, 2016

It would be better if the project can provide an option where it will a configuration file to read in linting specific folders or files instead of explicitly define them over the cli.

@overtrue
Copy link
Owner

@rmrhz Thanks, I will do it next version. 😄

@rmrhz
Copy link
Contributor Author

rmrhz commented Jul 27, 2016

Oh we posted it nearly at the same time ^_^

@overtrue
Copy link
Owner

@rmrhz 😆

@rmrhz
Copy link
Contributor Author

rmrhz commented Jul 27, 2016

Looking forward in the next iteration 谢谢你 :D

@overtrue
Copy link
Owner

@rmrhz ❤️

@overtrue
Copy link
Owner

@rmrhz do you perfer to using yaml or php to config the project ?

@rmrhz
Copy link
Contributor Author

rmrhz commented Jul 27, 2016

@overtrue hmmm, considering interoperability we could go with both ways. lets try yaml for now as it would be easier to parse through and through.

@overtrue
Copy link
Owner

overtrue commented Jul 27, 2016

@rmrhz

.phplint.yaml:

path: ./app
jobs: 5
extensions:
  - php
exclude:
  - vendor

.phplint

return [
    'path' => './app',
    'jobs' => 5,
    'extensions' => ['php'],
    'exclude' => ['vendor'],
];

@rmrhz
Copy link
Contributor Author

rmrhz commented Jul 27, 2016

@overtrue looks great 👍

@abrahamgreyson
Copy link

vot for yaml

overtrue added a commit that referenced this issue Jul 27, 2016
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