We receive a lot of feedback about why not the HTTP API use slug for all items ( products, features etc ). At this moment, the HTTP API is based on resource id's and this experience is not the best for some scenarios like Azure DevOps Task, Esquio CLI etc..
For Esquio 2 we need to consider using slug on our HTTP API.
Well,
We receive a lot of feedback about why not the HTTP API use slug for all items ( products, features etc ). At this moment, the HTTP API is based on resource id's and this experience is not the best for some scenarios like Azure DevOps Task, Esquio CLI etc..
For Esquio 2 we need to consider using slug on our HTTP API.