3 ms·

Really cool product and a well-done demo. I noticed that the autocomplete didn't work for the co2 service (e.g. host says "I think it's response.ppm" rather tha

Really cool product and a well-done demo. I noticed that the autocomplete didn't work for the co2 service (e.g. host says "I think it's response.ppm" rather than ppm being suggested. This despite the co2 service (presumably) being developed and published with autocode as well. The pervasive auto-complete and composability make the offering really compelling, but it's unfortunate that (at least in that example) the two don't work together. On a related note it would be lovely to use (or allow) typescript and publish TS declaration files and thin generated clients for APIs deployed on autocode. These are both minor nits in an otherwise impressive offering. Both are likely "next iteration" features since it seems like you've already solved a lot of the hard problems and these would be connecting existing dots together.

keithwhor 7y ago
Thank you. It means a lot. The reason `result.ppm` didn't autocomplete was because I didn't specify a return schema when I built the service. It's up to the developer who builds the API to specify nested object schemas via the FunctionScript specification [0] and I hadn't. It was a long day and I didn't feel like re-recording the entire video. :) Long way of saying -- it'll work if you want it to. TS could be neat, it's conceptually not difficult, the question of implementation is ultimately: where does our team's time go as we continue to roll out features for business users? About half of our users are not professional developers so balancing between pro / not-pro is part of what makes our roadmap planning interesting. [0] https://github.com/FunctionScript/FunctionScript https://github.com/FunctionScript/FunctionScript