entlicher commented on pull request #2995:
URL: https://github.com/apache/netbeans/pull/2995#issuecomment-861369065
> I agree that the semantics of actions in configurations are getting more
and more complicated.
>
> Can't we stick to existing API? And just: if project's
`ProjectConfigurationProvider != null` and `configurationsAffectAction(action)`
and not `ActionProvider.isActionEnabled(action, singleton(configuration))` then
don't show the action?
>
> Why? Because the action is _affected by configurations and currently
disabled_ - e.g. not available in current configuration.
This approach is not usable for me.
Because of this condition in gradle's
`ConfigurableActionsProviderImpl.findActionProvider`:
```
if (m == null) {
m = getActionData(GradleExecConfiguration.DEFAULT).getAction(action);
}
```
It defaults to the DEFAULT configuration. And this is exactly what I do not
need. It makes sens to add only actions that differ in the configurations.
I must not include debug of continuous mode. And this would add it.
I'm not that experienced in projects, but I did not find an existing API
that would suit the intended use-case.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
