Make Constants public about hidden-secrets-gradle-plugin HOT 6 CLOSED

@Mazorius thanks for the suggestion, it would not be hard to make them public but do you see any use case of this public constants for our plugin users ?

from hidden-secrets-gradle-plugin.

If you write a custom plugin which applies your plugin or you want to extend or reconfigure the your created tasks.

I think currently a developer needs to hope you will not change the names in the future as they declare this names as strings instead of using your well defined constants.

For example I used the SonarQube plugin in my projects an need to say ... with the sonarqube plugin do this.
Much better would it to use a constant so SonarQube can change their plugin name and I do not care as developer. Because I am using the constant which they will change ;-)

from hidden-secrets-gradle-plugin.

Thanks @Mazorius , done in #20 to be able to use them in tests, if you can check the code please ;)

from hidden-secrets-gradle-plugin.

Looks good ;-)

from hidden-secrets-gradle-plugin.

Maybe you will check the constants content in tests so that changing them will result in test failures?

from hidden-secrets-gradle-plugin.

@Mazorius I agree with you, done in #20

So I close this issue ;)

Thanks

from hidden-secrets-gradle-plugin.