Long filenames causing issues on Windows

[svrooij]

What are you generating using Kiota, clients or plugins?

API Client/SDK

In what context or format are you using Kiota?

Nuget tool

Client library/SDK language

Python

Describe the bug

Kiota generates to long filenames for some models in the Graph api.

Which causes issues when trying to install the python graph sdk on Windows without support for long filenames.

microsoftgraph/msgraph-sdk-python-core#338

Expected behavior

I expect the filenames of the models to be truncated to 30 (or other defined number) chars and then made unique.

How to reproduce

microsoftgraph/msgraph-sdk-python-core#338

Open API description file

Graph specs

Kiota Version

1.0.0

Latest Kiota version known to work for scenario above?(Not required)

No response

Known Workarounds

No response

Configuration

No response

Debug output

Click to expand log

```

</details>


### Other information

Personally I also faced this issue when I wanted to checkout the graph SDK for dotnet, but most SDKs are distributed compiled. In case of python the users of the api are faced with this issue as well, it no longer only bugs contributors but also end-users of the python sdk

[baywet]

Hi @svrooij
Thank you for using kiota and for reaching out.

This is something we're unlikely to change at this point since:

• changing the emitted paths also impacts the imports, which would be a breaking change.
• it's a windows only issue
• long path support is available since windows 10 1607 and only windows 10 1507 is still supported for security updates for another 8 months without this support. There are still a few windows server versions that are supported and do not offer long path support, but not for much longer, and that's most likely an extremely small audience at this point.

Let us know if you have any additional comments or questions.

[svrooij]

I have no personal gain with this issue, I refuse to install python on Windows 😬

Those reasons are perfect to not do anything about this, just wanted to get this issue on the radar and maybe close the other issue (3y old), as you already done.