Loading Profile...
Commands written using old API
Version 0.5pre2
I see that a lot of the built-in commands/feeds are marking commands as "old api" and thus disabling them.
I also keep getting periodic warnings about verbs not being able to be parsed in Parser 2 and such.
The parser warnings don't bother me but when commonly used commands like "define" stop working, that's a show-stopper!
Comments? Thanks. Keep up the great work.
I see that a lot of the built-in commands/feeds are marking commands as "old api" and thus disabling them.
I also keep getting periodic warnings about verbs not being able to be parsed in Parser 2 and such.
The parser warnings don't bother me but when commonly used commands like "define" stop working, that's a show-stopper!
Comments? Thanks. Keep up the great work.
I’m anxious
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?vikasa, could you please try upgrading to the final 0.5 which was released last week? That may solve your problems with define, for starters.
If you have any custom commands which need updating, clicking on the "old API" badge will send you to a command conversion tutorial. Hope that helps. :)
The company says
this answers the question
-
EMPLOYEE
