fairfield-programming / eaf-linter Goto Github PK

Idea

I just learned that duplicate lines are a problem in large codebases. So, we should make a system that detects duplicate chunks of code. This duplicate detector should not fire off if there are a few similar lines, but it should be triggered when an entire function is duplicated, or giant chunks of code are duplicated a bunch.

This detector can either be built using plaintext or by using the abstract syntax tree generated by the babel parser. I think that the system would be much more powerful if we build it using the babel parser.

https://linearb.io/blog/code-duplication/

Todo

• Build a system to detect important code chunks using the babel parser
• Store the important code chunks
• Check in the code where the important chunks of code are repeated

Idea

Right now, we have a ton of features, we just need to start documenting them. So, I've added readme files to the pages that need them. If you want to write a bit about this feature, just leave a comment and I will assign you to the issue.

For the beautifier, it's not done yet, but just write about the features it will have. It will be a pretty ordinary beautifier but what makes it different is that it will support tons of different coding styles. Most alternative beautifiers don't support that, so it will make this one very special.

https://github.com/fairfield-programming/eaf-linter/tree/master/src/linter

Todo

• Add in Readme to Beautifier Page

Idea

Right now, we have a ton of features, we just need to start documenting them. So, I've added readme files to the pages that need them. If you want to write a bit about this feature, just leave a comment and I will assign you to the issue.

For the performer, you just need to add a couple more sentences about what makes the performer special, and maybe just make it look a little prettier. You don't need to do much, but any help would be appreciated.

https://github.com/fairfield-programming/eaf-linter/tree/master/src/performer

Todo

• Add in Readme to Linter Page

Idea

I'm getting really annoyed because my code keeps failing because this library isn't done yet. To fix this, I'm adding the option to ignore test failure in the options.

Todo

• Add in a parameter check in the readme

Idea

We really need to make this project more popular. The way we can do this is by getting onto Github Explore because then we will get a ton of stars. There is an explore collection just for this here that you can just add our repository into and then create a pull request.

Todo

• Send in a pull request to Github Explore with our repository

Idea

We want this library to be as simple to use as possible, but also it needs to be modular and customizable. So, what we need now is the ability for users to configure the path for their testing files. And, this isn't going to be a static path but rather, they are going to specify a regex pattern and we will see if that pattern matches any of their files. If the pattern matches, we will test that file.

Todo

• Add in a parameter to look for in the package.json so people can specify where they want to keep their test files
• Allow them to put in regex as the parameter
• Replace the current code with their regex when checking for the testing path

Idea

Right now, we have a ton of features, we just need to start documenting them. So, I've added readme files to the pages that need them. If you want to write a bit about this feature, just leave a comment and I will assign you to the issue.

For the linter, it's not done yet, but just write about the features it will have. It will be a pretty ordinary linter but what makes it different is going to be a pipeline approach to plugins and focusing on comments in the linting process.

https://github.com/fairfield-programming/eaf-linter/tree/master/src/linter

Todo

• Add in Readme to Linter Page