improve of finding .jscsrc behavior

[golyshevd]

Hi! In our project we need to use more than one codestyles. We tried to put .jscsrc in subdirectory where used another than default codestyle

/.jscsrc
/other-code-style/
    my-file.js
    .jscsrc

checker.checkFile('./other-code-style/my-file.js');

But jscs finds .jscsrc up from cwd or from passed directory, not from filePath. And we had to use the second call of jscs for other-code-style directory. In my opinion jscs should use other-code-style/.jscsrc file for other-code-style/my-file.js.

I understand that it is too expensive to find .jscsrc for each checkFile call, but isn't that native behavior?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[jedireza]

👍 I'd like this to travel all the way back to my home directory ... that way I could have ~/.jscsrc as a default.

[mikesherov]

/cc @markelog @mdevils I'm tempted to put this into 1.9. What are your guys thoughts?

[mdevils]

@mikesherov this seems very hard to implement correctly... I have some ideas on how to do it (improving Configuration). I can take this issue.

[hzoo]

We released 3.0 recently! We also wrote a post about how 3.0 will be our last major release (since we are deprecating the project) and that we are merging with ESLint!

Thus we won't be working on any new features moving forward which includes new rules/options. We will continue to fix bugs and work on CST/better autofixing for current rules in the upcoming months both to help JSCS users and to gain experience that we can hopefully use in ESLint. But otherwise we both teams will be working on getting ESLint feature parity with JSCS and just a nice transition for our users.

I'm putting an orphaned label to note this issue isn't planned to be worked on.