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

more suggestions #293

Closed
gurgeous opened this issue Mar 13, 2018 · 7 comments
Closed

more suggestions #293

gurgeous opened this issue Mar 13, 2018 · 7 comments

Comments

@gurgeous
Copy link
Contributor

I may have some time available to work on the extension. Here are some tasks I am interested in tackling. These are not in order. Are any of these of interest? Suggestions welcome:

  1. support for rufo formatting, or at least disabling rubocop formatting
  2. better user facing error/debug messages for rubocop linting/formatting
  3. more updates to the readme (to help people with config issues)
  4. add more tests
  5. old issue triage

?

@gurgeous
Copy link
Contributor Author

Oh, and perhaps this:

  1. enable/run tslint and prettier on our code

@wingrunr21
Copy link
Collaborator

  1. Support Rufo for formatting #295
  2. Rubocop/linting needs a ton of work in general
  3. Yep, thanks for your work starting that out
  4. Yep
  5. I'm pretty close to just closing all issues except those opened since about last November as the I'm not sure many of them reflect the current state of the project.
  6. That is not in this project's scope. Why do the TSLint/ESLint extensions not do that job?

@gurgeous
Copy link
Contributor Author

Oh, for (6) I mean running tslint/prettier on the extension source itself (i.e - prettier src/ruby.ts) to catch errors and reformat our code in a standard way. I agree it would be silly to build them into vscode-ruby :) Sorry for the confusion.

@wingrunr21
Copy link
Collaborator

ohhh, gotcha. Yep, that sounds good to me.

@gurgeous
Copy link
Contributor Author

For (2), see #297

@gurgeous
Copy link
Contributor Author

For (6), see #299. Seems important since one of my PRs already ran into trouble with formatting.

@gurgeous
Copy link
Contributor Author

I'd be happy to help with (5), but I think you'd have to make me an admin. Reading the old issues would also be a good way to start creating a FAQ for the README. Let me know if you want help along those lines.

@gurgeous gurgeous closed this as completed Apr 5, 2018
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

2 participants