Generic tasks don't support Name attribute

[jhorrocksParticipant]

Just wanted to report an issue we noticed in case it’s a bug. If you decorate a generic task with the Name attribute to provide a custom name, you’re no longer able to select the generic type. Instead it chooses one type and forces you to use that. We were using a constraint on the generic so I’m not sure if that was affecting it. Once the Name attribute is removed it works as expected.

[GavalakisKeymaster]

Hello,
Thank you for the report.
This was a known bug indeed, and which has now been fixed in the latest version that has recently gone live on the asset store! 🙂

If you encounter anything else, please let me know.
Thanks.

[Author]

Posts