-
Notifications
You must be signed in to change notification settings - Fork 198
allow other projects to use extends for our tslint.json #265
Comments
@HamletDRC Thanks for your work on this. Absolutely amazing job! I may be wrong, but I believe that in order for other projects to reference this using So, in this case, it would be I was getting errors in Atom until I went in and made that change. 👍 |
Also, after making that change and simply adding it using That said, because those two rules aren't documented and I'm not really sure what they are, it may very well just be an issue on my side, but I figured I'd toss this out there as well. For now , I just changed those two rules to Thanks again! |
@dsifford For the rulesDirectory... I think that you need to add a rulesDirectory for tslint-microsoft-contrib in your main tslint configuration. Did you have a rulesDirectory already in your config? How do you run tslint, from command line or grunt? |
@HamletDRC Thanks for the info Re: You are correct that the Totally up to you, though I still would prefer it defined on your end. Thanks so much again for your work on this. Super, super impressive! |
Sure, I can add this. However... I won't cut a new release for it unless there is some other larger, more critical issue. Thanks for the kind words. You know... you're free to help out. It's just a simple "git clone && npm install && grunt create-rule --rule-name=my-cool-rule" away :) |
Whoops, missed this question! I run it both from the command line and also using the linter-tslint Atom package. |
I think it would be useful to add this info to README, e.g. here, something very simple like:
examples:https://github.com/palantir/tslint-react#usage should I submit a PR? |
@vyorkin I updated the readme. If you'd like to add/edit anything then feel free to submit a PR. |
for PR #263
The text was updated successfully, but these errors were encountered: