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

NEW CHECKERS IN PRIORITY – SEE MILESTONES #143

Open
Antonboom opened this issue Jun 21, 2024 · 7 comments
Open

NEW CHECKERS IN PRIORITY – SEE MILESTONES #143

Antonboom opened this issue Jun 21, 2024 · 7 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Antonboom
Copy link
Owner

Antonboom commented Jun 21, 2024

Hi, everyone!

I appreciate your contribution to testifylint, but at the moment the project has not yet entered the stabilization phase, but is maintaining a strategy for unrealized functionality.

Thus, we should concentrate on the implementation of new checkers, and not on multi-day discussions about whether Empty is suitable for typed zero or not (relatively speaking).

After the minor release, we can waste some time (e.g. not more than two) to other issues (related to old checkers).
And to begin to focus on the next milestone:
https://github.com/Antonboom/testifylint/milestones

Checkers can be implemented in any order, the milestones above are my vision of priorities.
If some checkers implementation are awaiting my feedback, that feel free to ping me.

Thank you!

@Antonboom Antonboom added the good first issue Good for newcomers label Jun 21, 2024
@Antonboom Antonboom pinned this issue Jun 21, 2024
@Antonboom
Copy link
Owner Author

(cc) @ccoVeille @mmorel-35

@Antonboom Antonboom added the enhancement New feature or request label Jun 21, 2024
@ccoVeille
Copy link
Contributor

ccoVeille commented Jun 21, 2024

OK, noted.

I'm sorry if my remarks leads to noise and distraction.

I was focused on empty because it was making sense for me, and my codebase.

Also, I was looking at these kind of issues because it's easier to contribute by updating/changing an existing linter than creating a new one.

But, I now understand better what you expect. It's a good thing to have a clear roadmap.

@ccoVeille
Copy link
Contributor

One thing that also leads me to create issue is because it's the only way for me to communicate with you.

I think it would be better if we could have another way to discuss and talk about things.

Here are the option I'm thinking about:

  • enable discussions on project
  • define a way to reach each other. I'm on discord and Gopher's Slack

What do you think about it?

@Antonboom
Copy link
Owner Author

enable discussions on project

I thought about it too. Done 👌

@mmorel-35
Copy link

Hi @ccoVeille ,
Please send me an invite to join https://gophers.slack.com/
I'm not a member yet.

@ccoVeille
Copy link
Contributor

It said unable to send invite. I will have to check, and maybe contact the admin of this community

@ccoVeille
Copy link
Contributor

ccoVeille commented Jun 26, 2024

@Antonboom Antonboom changed the title NEW CHECKERS IN PRIORITY NEW CHECKERS IN PRIORITY – SEE MILESTONES Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants