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

Custom checks through command line #774

Closed
wants to merge 13 commits into from
Closed

Custom checks through command line #774

wants to merge 13 commits into from

Conversation

ankita240796
Copy link

@ankita240796 ankita240796 commented Jan 13, 2018

closes #702

  • Added mechanism to specify a custom checks folder.

@rriemann
Copy link

Would it be possible to configure the checks folder also in the .proselintrc?

@rriemann
Copy link

I have installed proselint as root. However, when I run this command, it fails because of missing rights or because the folder "." exists already.

It must be clear that this command changes the system configuration permanently.

@ankita240796
Copy link
Author

ankita240796 commented Jan 19, 2018

@rriemann That was a good suggestion! I have added the feature to configure custom checks to .proselintrc.

@rriemann
Copy link

So if I have a checks folder configured in my ~/.proselintrc, on every call of proselint, all (new) files will be copied to the checks directory?

Is there a check in the code if the destination directiory in writeable?

@ankita240796
Copy link
Author

ankita240796 commented Jan 19, 2018

When a command line option check is used with an input path, the specified directory gets copied to checks folder and the checks are marked as true in .proselintrc.

@suchow
Copy link
Member

suchow commented Mar 23, 2018

Hi @ankita240796, thank you for the PR! :)

Would it be possible to:

  1. Split this PR into two smaller PRs, one that adds the custom path feature and another that adds the custom checks feature? I'm ready to accept the former immediately, but need to think more deeply about the latter.

  2. Add documentation to the "Checks section" of the README and to the docs showing how to use the custom path feature?

@ankita240796
Copy link
Author

Sure @suchow I will make the changes as suggested by you!

@jima80525
Copy link

Will this change cover the case where the user wants a custom .proselintrc file in the current directory?

I'm willing to add that feature if not, as I'd like to use this tool in an automated toolchain (on circleci) but I'd rather have the rc file be part of my repo, not requiring it to be in the ~ directory.

@ProselintBot
Copy link

ProselintBot commented May 5, 2018

Proselint found issues

README.md

Line Message Severity
66 Comparison of an uncomparable: 'very unique.' is not comparable. warning
66 Substitute 'damn' every time you're inclined to write 'very'; your editor will delete it and the writing will be just as it should be. Found 7 times elsewhere. warning
135 Comparison of an uncomparable: 'very unique"' is not comparable. warning
212 RAS syndrome. Use 'RAS' instead of 'RAS syndrome'. warning

Generated by 🚫 Danger

@ankita240796
Copy link
Author

ankita240796 commented May 5, 2018

Hi @suchow, sorry for delay on this. I was busy with my academics. I have made the changes as suggested by you. Please take a look, Thanks!

Also can you please help me with the failing build.

@ankita240796
Copy link
Author

Hi @jima80525, this change intended to add a feature for providing a custom location for .proselintrc but as suggested by @suchow, I have reverted that feature from this PR. I can submit another PR for that if you are not working on that feature, Thanks!

@ankita240796
Copy link
Author

Hi @suchow any updates on this?

@ankita240796 ankita240796 changed the title Custom checks and custom path to proselintrc through command line Custom checks through command line Jul 29, 2018
@ankita240796
Copy link
Author

I have also issued a separate PR for adding custom path: #865

@Nytelife26
Copy link
Member

Nytelife26 commented May 29, 2021

Custom checks are something I was thinking about earlier, so this is a nice surprise. I'll triage now and I'm fairly sure we implemented a config path already but I'll triage the other too.

@Nytelife26 Nytelife26 added the status: awaiting-triage Issues and PRs awaiting investigation and relabelling. label May 29, 2021
@ankita240796
Copy link
Author

Custom checks are something I was thinking about earlier, so this is a nice surprise. I'll triage now and I'm fairly sure we implemented a config path already but I'll triage the other too.

Ok Thanks @Nytelife26, let me know if I can help with something :)

@Nytelife26 Nytelife26 added priority: low Issues and PRs that should be resolved, but can be postponed. status: wip Issues and PRs that are still a work in progress. and removed status: awaiting-triage Issues and PRs awaiting investigation and relabelling. labels Jun 24, 2021
@Nytelife26 Nytelife26 added type: feat Issues and PRs related to new features. version: minor Issues and PRs with new features belonging to the next minor release. labels Jun 24, 2021
@Nytelife26
Copy link
Member

I'm not entirely sure copying the new checks into the checks folder is the best way to go about this. One would assume supplying a custom checks folder via CLI, rather than via configuration, persists solely for that command.

@ankita240796
Copy link
Author

I'm not entirely sure copying the new checks into the checks folder is the best way to go about this. One would assume supplying a custom checks folder via CLI, rather than via configuration, persists solely for that command.

Should I take that up and add a fix in this PR?

@Nytelife26
Copy link
Member

Nytelife26 commented Jul 4, 2021 via email

@ankita240796
Copy link
Author

ankita240796 commented Jul 6, 2021

Sure, I am working on this, will update once I finalize the design approach.

@ankita240796 ankita240796 deleted the extend branch July 11, 2021 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Issues and PRs that should be resolved, but can be postponed. status: wip Issues and PRs that are still a work in progress. type: feat Issues and PRs related to new features. version: minor Issues and PRs with new features belonging to the next minor release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

custom .proselintrc path
7 participants