Skip to content

How to make checks that Search first, Diagnose and Analyze later #826

Closed
@davidperezgar

Description

We have some checks to develop like Generic Names, Readme privacy and more.
What we need is to search for all functions used in a plugin, then analyze them and diagnose the problem.

We don't know how to approach this problem. What we see is that we show the error individually but we need to show globally.

For example in Generic Names, we have to look for functions/class/etc names and after analyze them for example in an array, and then show the problem.

So the check would be like:
Search Functions names > Make them in a list > Review and diagnose which are problematic > Make the error for each of them.

It's similar to the other Check related with privacy. We have to look al remotes calls, then see in the readme if the privacy notes are written, if not, warn to the user.

What do you think?

CC: @mukeshpanchal27 @felixarntz @swissspidy

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions