You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@audris I had a thought on how to streamline the syntax for the webAPI but I'm concerned about it deviating too much from how the actual scripts are executed. Right now, to execute this showCnt command: echo 009d7b6da9c4419fe96ffd1fffb2ee61fa61532a | showCnt.perl commit in the webAPI you do: curl "https://worldofcode.org/webAPI/showCnt?sha1=009d7b6da9c4419fe96ffd1fffb2ee61fa61532a&type=commit"
There are two problems that I have with this syntax:
If you provide more than one variable, you have to wrap the address in quotes
Multiple fields can be more confusing and a lot longer
My thoughts is that we change the way we call the webAPI to: curl https://worldofcode.org/webAPI/showCnt?commit=009d7b6da9c4419fe96ffd1fffb2ee61fa61532a
The key difference here is that instead of using a field for sha1 and a field for type, I instead specified my input as a commit and set it equal to the sha1, essentially keying the sha1 with the type. So another example for a tree would be: curl http://localhost:3000/webAPI/showCnt?tree=464ac950171f673d1e45e2134ac9a52eca422132
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
@audris I had a thought on how to streamline the syntax for the webAPI but I'm concerned about it deviating too much from how the actual scripts are executed. Right now, to execute this showCnt command:
echo 009d7b6da9c4419fe96ffd1fffb2ee61fa61532a | showCnt.perl commit
in the webAPI you do:curl "https://worldofcode.org/webAPI/showCnt?sha1=009d7b6da9c4419fe96ffd1fffb2ee61fa61532a&type=commit"
There are two problems that I have with this syntax:
My thoughts is that we change the way we call the webAPI to:
curl https://worldofcode.org/webAPI/showCnt?commit=009d7b6da9c4419fe96ffd1fffb2ee61fa61532a
The key difference here is that instead of using a field for sha1 and a field for type, I instead specified my input as a commit and set it equal to the sha1, essentially keying the sha1 with the type. So another example for a tree would be:
curl http://localhost:3000/webAPI/showCnt?tree=464ac950171f673d1e45e2134ac9a52eca422132
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: