name2key question

[Heyter Nitely]

Perfect,

another thing about name2key.

{“normalname”:”heyter nitely”,”name”:”heyter nitely”,”key”:”16fcc762-abdc-4c30-9591-9b9fd4c8dfaa”,”action”:”name2key”,”result”:”OK”}

There is no way for your function to return the exact name ? Meaning upper/lowercase in the “normalname” key at least

• This topic was modified 7 years, 9 months ago by Heyter Nitely.
• This topic was modified 7 years, 9 months ago by Glaznah Gassner.

[Glaznah Gassner]

Heyter,

I believe this question relates to HTTP API, so I moved it here.

The name2key function returns the name exactly as you pass it. Do you mean it should convert the name to its actual Second lower/uppercase view?

[Heyter Nitely]

Hi.

Yes, the function return the name as we pass it in both key normalname and name. It should be really useful to return the real name (with upper/lowercase) in the normalname key. For myself, it will prevent for me to use a dataserver event with the key returned to get the good view of the avatar name.

[Glaznah Gassner]

Heyter,

Please check new parameter request_case for these commands:

https://www.mysmartbots.com/dev/docs/HTTP_API/Bot_Commands/name2key
https://www.mysmartbots.com/dev/docs/HTTP_API/Bot_Commands/key2name

It ensures the correct name case retrieval

[Heyter Nitely]

Hi,

thank you very much for the change, would help me a lot

Will keep you updated if any error occur

[Heyter Nitely]

Hi !

I’m still using this function I just noticed that if you require the name “heyter” for example, it will return you “heyter resident” even if the parameter request_case is set to 1.

[Glaznah Gassner]

Hello Heyter. This is because your name got saved in the database in lower case (it has been added before we added the case resolution).

I’ll check the possible solution and notify you about the fix asap.

[Heyter Nitely]

Hi,

Thanks for reply.

[Author]

Posts