You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 5, 2021. It is now read-only.
I understand how the material naming convention works and how you order them using numbers; however, what I'm unsure of is whether or not you can force a custom name through.
In my specific example I want to have the material labeled Object-Oriented UX. This test case not only has a hyphen in it, but also multiple capitalization's in the word UX. Is there any way I can force through a custom name type that is different than the file name to avoid it being relabeled incorrectly?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I understand how the material naming convention works and how you order them using numbers; however, what I'm unsure of is whether or not you can force a custom name through.
In my specific example I want to have the material labeled
Object-Oriented UX
. This test case not only has a hyphen in it, but also multiple capitalization's in the wordUX
. Is there any way I can force through a custom name type that is different than the file name to avoid it being relabeled incorrectly?The text was updated successfully, but these errors were encountered: