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

Rewriting linter-javac in ES(6?) #76

Open
14 tasks
florianb opened this issue Feb 18, 2016 · 5 comments
Open
14 tasks

Rewriting linter-javac in ES(6?) #76

florianb opened this issue Feb 18, 2016 · 5 comments

Comments

@florianb
Copy link
Contributor

florianb commented Feb 18, 2016

I am currently working hard making bugs testable, ironing bumps out and enhance the use of classpaths in general.

It unfortunately seems to be a huge effort to make the linter-javac-plugin 🚬-testable without touching the plugin itself. I currently don't want to add any untested functionality to prevent delivering a failure to our users.

Therefore i file this issue to collect ideas and feedback on the rewrite which will be accomplished with the "Release 2.0.0"-Milestone.

🎅 Wish List

Every wish will become a separate issue, to allow us the detailed discussion of concerns.

Help me

  • finding ideas
  • give feedback on the codebase
  • create PR's
@florianb
Copy link
Contributor Author

Proof the implementation of performance tests.

@Arcanemagus
Copy link
Member

I recently put performance metrics into linter-jscs (implemented testing a bug and decided to put it in there for good). You can check out how I did that here as an inspiration.

@florianb
Copy link
Contributor Author

florianb commented Jun 6, 2016

Great idea - thanks @Arcanemagus. I guess i'll implement something similar.

@Justsnoopy30
Copy link

Is this project abandoned or forgotten about? Nothing has progressed for 4 years.

@florianb
Copy link
Contributor Author

florianb commented Mar 29, 2020

No. I don't use Atom anymore and i don't program Java currently. So i felt no pressure about it.
Feel free to contribute.

@florianb florianb removed their assignment Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants