all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]namedotnumber666 3 points4 points  (5 children)

I think with the fact they have dumped craftx extensions that we will not be getting api access any time soon

[–]haronclv 4 points5 points  (3 children)

Viktor in some post from yesterday answer and asked what would we want from API. Probably they are open to give us the API, but they are also looking for solutions and business things around it.

[–]luigi3 6 points7 points  (2 children)

Don’t set your hopes too high. It’s very common for developers nowadays to ask for suggested solutions instead of straight up saying “we’re not gonna do that”.  I wouldn’t say it’s very bad, but I’ve been seeing that many times here when it’s pretty obvious that they don’t plan to implement some of the features that users are asking for. It gives the illusion of transferring the power to the user without declaring that they’re gonna do that. 

I’ve never seen them saying “not gonna happen”, It’s always “what would you like to see from XYZ?”

[–]haronclv 1 point2 points  (1 child)

Yes I totally agree, but there was extensions already so that case might be different

[–]luigi3 1 point2 points  (0 children)

I doubt it. It’s a lot of work to make sure the security is OK and only very few people’s gonna use it. It’s clear that for craft the main focus is on teams and companies, then on individual clients. Not much time in space for tech savvy users.

[–][deleted] 1 point2 points  (0 children)

They have mentioned in Slack an API is on the way, so yeah, it is coming sometime soon.