Hi, somone has raised this valid issue with uSync rc. around how we do custom operation ids. 
https://github.com/KevinJump/uSync/issues/629 and in it they point to the docs. 
https://docs.umbraco.com/umbraco-cms/reference/api-versioning-and-openapi#adding-custom-schema-ids which in summary say.
- override Umbraco's 
OperationIdSelector
 with something that checks for your api end point and then only applies that. 
- replace umbracos in a build 
builder.Services.AddSingleton<IOperationIdSelector, MyOperationIdSelector>();
my convern here is that this isn't sustainable ? 
if i register 
.AddSingleton<IOperationSelector, uSyncOperationSelector>
and then someone else comes along and reigsters 
.AddSingleton<IOperationSelector, SuperCustomIdSelector>
 
doesn't that mean that my customId selector will never then be used ? 
---
I think (and i might be wrong) that what i should actually do, is only register my custom selector on the site i am using to generate my API from and not actually put it in the solution ? because as far as i can tell once the typescript files have been generated they are using the path not the id, so it doesn't matter ?