API Returns 'None' for Description from list_smb_shares

I have used one of the examples to get the detail of our SMB shares, as I need to clone them to our DR cluster.

Mostly it works as expected, this is a fragment:

api_response = protocols_api.list_smb_shares(sort=sort, limit=limit, dir=sdir, scope=scope) pprint(api_response)

I have scope set to "user" so that it should return only the non-default values.  In fact it returns all values with the defaults set to None; that is fine but the Description is returned as None when it is not blank at all:

{'resume': '1-1-MAAA1-MAAA1-MgAA1-MAAA0-1-MQAA4-NTA3MAAA4-NTA3MAAA', 'shares': [{'access_based_enumeration': None,              'access_based_enumeration_root_only': None,              'allow_delete_readonly': None,              'allow_execute_always': None,              'allow_variable_expansion': None,              'auto_create_directory': None,              'browsable': True,              'change_notify': None,              'create_permissions': None,              'csc_policy': None,              'description': None,              'directory_create_mask': None,

If I use the CLI to list this in JSON format I can see the Description is not blank:

rothstore1-2# isi smb shares list --limit 1 --format json [{"file_create_mode": 64, "ntfs_acl_support": true, "directory_create_mask": 448, "access_based_enumeration_root_only": false, "file_create_mask": 448, "path": "/ifs/roth/projects/2020wheatm", "inheritable_path_acl": false, "allow_variable_expansion": false, "id": "2020wheatm", "hide_dot_files": false, "create_permissions": "default acl", "strict_locking": false, "mangle_map": ["0x01-0x1F:-1", "0x22:-1", "0x2A:-1", "0x3A:-1", "0x3C:-1", "0x3E:-1", "0x3F:-1", "0x5C:-1"], "zid": 1, "run_as_root": [], "browsable": true, "description": "John Doe\n",

If I set the scope to "effective" I do get the Description back from the API:

'description': 'John Doe\n',

And lastly if I set the scope to "default" I get from the API:

'description': 'Isilon OneFS',

It does not seem to work as expected.  The point of the "user" scope is that I don't need to do anything about values that return "None" as they have not been customised.  I'm wondering if the \n is causing a problem under the hood.  When I was testing json.loads and giving it a static string (pasted from the CLI output) it objected to the \n.  However that wouldn't explain the behaviour of scope "effective".

I'm thinking a bug in the code determining that the Description is a string but the string isn't 'Isilon OneFS'.