Max: Implementation of the validator for model name

[moonyuet]

Changelog Description

Ported from Openpype: ynput/OpenPype#6164
Implement the validator for model name in 3dsmax

Additional info

The validation regex by default is (.*)_(?P<subset>.*)_(GEO) and
your model name should be {Some name}_{SubsetName}_GEO

Testing notes:

1. Go to OP/AYON Settings
2. Turn on Validate Model Name
3. Set your preferred validation regex for checking your model name
4. Validate Model Name would check your name accordingly with your validation regex

[LiborBatek]

Im getting this error when validating the publish:

DEBUG: ['TeaCup01']
Traceback (most recent call last):
  File "C:\Users\lbate\AppData\Local\Ynput\AYON\dependency_packages\ayon_2402141620_windows.zip\dependencies\pyblish\plugin.py", line 527, in __explicit_process
    runner(*args)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 96, in process
    invalid = self.get_invalid(instance)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 49, in get_invalid
    invalid_model_name = cls.get_invalid_model_name(instance, name)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 61, in get_invalid_model_name
    current_asset_name = instance.context.data["asset"]
KeyError: 'asset'

[moonyuet]

Im getting this error when validating the publish:

DEBUG: ['TeaCup01']
Traceback (most recent call last):
  File "C:\Users\lbate\AppData\Local\Ynput\AYON\dependency_packages\ayon_2402141620_windows.zip\dependencies\pyblish\plugin.py", line 527, in __explicit_process
    runner(*args)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 96, in process
    invalid = self.get_invalid(instance)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 49, in get_invalid
    invalid_model_name = cls.get_invalid_model_name(instance, name)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 61, in get_invalid_model_name
    current_asset_name = instance.context.data["asset"]
KeyError: 'asset'

Im getting this error when validating the publish:

DEBUG: ['TeaCup01']
Traceback (most recent call last):
  File "C:\Users\lbate\AppData\Local\Ynput\AYON\dependency_packages\ayon_2402141620_windows.zip\dependencies\pyblish\plugin.py", line 527, in __explicit_process
    runner(*args)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 96, in process
    invalid = self.get_invalid(instance)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 49, in get_invalid
    invalid_model_name = cls.get_invalid_model_name(instance, name)
  File "C:\Work\REPO\ayon-core\client\ayon_core\hosts\max\plugins\publish\validate_model_name.py", line 61, in get_invalid_model_name
    current_asset_name = instance.context.data["asset"]
KeyError: 'asset'

This happens mainly because the instance.context.data["asset"] switched to instance.context.data["folderPath"] in AYON. Should be working now with the latest commit.

[LiborBatek]

All works as expected.
Validator correctly kicks in. Select Invalid select the non valid geometry

And if correct then validates properly without error:

[antirotor]

I think we should make it more artist friendly, especially validator that will trigger probably very often. I know that we are not using it on many places, but publisher has already ability to show stuff.

Look at https://github.com/ynput/ayon-core/blob/develop/client/ayon_core/hosts/maya/plugins/publish/validate_node_ids.py

Maybe not the greatest example, but it is using PublishXmlValidationError and xml file located in help directory.

I do understand that this is pretty straightforward validation that is requiring simple action from artist, so I stating it here mainly as a reference.

[antirotor]

apart that json file it looks a works great

[antirotor]

this shouldn't probably be here in this PR

[antirotor]

great, thanks for the changes!