I understand the value of catching typos early in the workflow! However, Spine doesn't currently have a built-in spell checker.
Workarounds you can use:
Export to JSON for review: You can export your skeleton data to JSON format with Nonessential data checked. JSON files are human-readable, making it easier to review names and catch typos. If you find errors, you can either:
- Fix them in Spine and re-export
- Edit the JSON directly and then use Import Data to bring the corrected data back into your Spine project
External text editors: Open the exported JSON in a text editor with spell-checking capabilities to identify typos before finalizing your export.
Naming conventions: Establish clear naming conventions for your team to minimize typos from the start.
While this isn't as seamless as having spell-checking built directly into Spine, the JSON export/import workflow gives you a way to catch and correct errors before your data reaches the runtime.
This is good feedback for a potential future feature!
