Skip to content
New issue

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

Synced Folder names are made to be lower case #74

Open
2 tasks done
nikshankarnoble opened this issue Sep 7, 2024 · 2 comments
Open
2 tasks done

Synced Folder names are made to be lower case #74

nikshankarnoble opened this issue Sep 7, 2024 · 2 comments

Comments

@nikshankarnoble
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

Right now, when a Folder is synced across from Kitsu it's name is forced to be lower case as part of the slug-ification, so for example an asset cameraA in Kitsu will be created in AYON as cameraa. The label will still be correct as that's just copied straight across.

Expected Behavior:

As AYON Folders support upper case characters in their name, I would expect the name to be synced across to match if the entity name in Kitsu is already a valid name in AYON. This isn't a big deal as we should be linking them through their kitsuId metadata anyway, but it can cause some unnecessary confusion when the asset name in UIs and on disk don't match Kitsu

Version

1.0.0

What platform you are running on?

Linux / Centos

Steps To Reproduce:

  1. Ensure that the Kitsu service is setup in AYON.
  2. Create a new entity in Kitsu with capitals in the name, e.g bobLoblawA
  3. The created Folder in AYON will have a name of bobloblawa

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

No response

@nikshankarnoble
Copy link
Author

@martastain @BigRoy it looks like Tasks have this same behaviour - are you happy for this to be changed to match capitalisation in names for both Tasks and Folders? If so I'm happy to raise a PR for this change! :)

@nikshankarnoble
Copy link
Author

Also - unrelated to this issue but a couple of inconsistencies I ran into with the support form for raising this issue (which is great by the way!):

  • I was only able to select 1.0.0 as the version for the addon, but this was actually with v1.2.3
  • I had to select that I'd added all the relevant labels to the bug report, but I don't seem to have the ability to add labels to an issue (perhaps I missed it but I don't think so).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant