Closed ErnSur closed 1 year ago
Should we add an option to format field names to your liking? Like adding a prefix to generated field names.
added code gen settings in a form of new UXML root tag attributes.
code-gen-prefix="_"
attribute can be added to UXML root tag.
should the generated cs file always be in the same dir as UXML or should the user be able to relocate generated script? if so how to ensure that the regenerated script overrides the old one? if we want to allow relocation of this file we need to track it somehow for the autogeneration feature.
For now, the generated cs file will stay in the same directory as the UXML file. This solution is the easiest to maintain and for now, I don't see any problems with that. If the user wants generated cs file to belong to a certain assembly he can use assembly definition and assembly definition reference assets.
Option to Toggle automatic generation for a UXML file save toggle value to AssetImporter.userdata?
To use this feature user needs to manually trigger cs generation from the context menu button of VisualTreeAsset
. Then each time this UXML changes the cs file will be regenerated automatically.
All that is left to do:
TODO:
UxmlNamespacePrefixAttribute