We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AddComponentMenu
Unity doesn't sort scripts into a nice collapsible folder structure based on the namespace in the component picker.
They rely on an [AddComponentMenu] attribute to be added to each class to tell Unity how best to organise the component in the component picker.
[AddComponentMenu]
A way of having Malimbe apply this attribute to an entire namespace would be a great time saver.
Maybe that Malimbe weaver just takes the whole config in the config file instead of any attributes. Something like
• NamespaceRegex="^Zinnia" Hidden="false" • NamespaceRegex="^Tests.Zinnia" Hidden="true"
NamespaceRegex="^Zinnia" Hidden="false"
NamespaceRegex="^Tests.Zinnia" Hidden="true"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Unity doesn't sort scripts into a nice collapsible folder structure based on the namespace in the component picker.
They rely on an
[AddComponentMenu]
attribute to be added to each class to tell Unity how best to organise the component in the component picker.A way of having Malimbe apply this attribute to an entire namespace would be a great time saver.
Maybe that Malimbe weaver just takes the whole config in the config file instead of any attributes. Something like
•
NamespaceRegex="^Zinnia" Hidden="false"
•
NamespaceRegex="^Tests.Zinnia" Hidden="true"
The text was updated successfully, but these errors were encountered: