[Drop.io API] Create A Drop - Default View not optional

2 views
Skip to first unread message

Karl Freeman

unread,
Apr 17, 2010, 9:54:05 AM4/17/10
to Drop.io API
Sorry for a whole post about this but its just to let you know that
when creating a drop using the 2.0 api and specifying a default_view I
get 500 error's when its empty. Its easy to work around by setting a
default my side but unless you specify eg "media" the api query fails.
Perhaps you could set on your side a default when the default_view is
empty or not a correct string?

Cheers
Karl.

--
You received this message because you are subscribed to the Google Groups "Drop.io API" group.
To post to this group, send email to dropi...@googlegroups.com.
To unsubscribe from this group, send email to dropio-api+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dropio-api?hl=en.

Karl Freeman

unread,
Apr 17, 2010, 9:55:34 AM4/17/10
to Drop.io API
Also I wondered if perhaps another idea ( im full of them today ;) )
would be some sort of ticketing system? Like I feel a little guilty
doing a whole post to all the developers about something minor about
the api?

Keep up the hard work!
Karl.

ja...@dropio.com

unread,
Apr 17, 2010, 12:17:11 PM4/17/10
to dropi...@googlegroups.com
That's a good idea Karl. We were looking at the tools twitter uses for their API and they have a bugtracker in google code. I'll talk about it with Eric, he's busy organizing barcamp this weekend but I think he has some thoughts about how we should manage api tracking.

Jake Good

unread,
Apr 19, 2010, 11:26:34 AM4/19/10
to dropi...@googlegroups.com
So I've found the issue and we're talking about the resolution
internally...

One of the key balances in play here is what the intent is vs. what is
valid input.

One could argue that a blank string value could be bad input and thus
it should error out (granted it should give a better error than a
500)...

But on the other hand, empty form values are kind of normal in the
HTML world, so would that be valid input in an API world?

I think we are a little *inconsistent* on a few parameters wether they
are blank or non-existing... I know for a fact that the Ruby library
sends nil/empty values along by default on a lot of parameters...

We'll discuss this internally but would welcome any suggestions from
you guys...

Jake Good
http://dev.drop.io
> For more options, visit this group at http://groups.google.com/group/dropio-api?hl=en
> .
>
> --
> You received this message because you are subscribed to the Google
> Groups "Drop.io API" group.
> To post to this group, send email to dropi...@googlegroups.com.
> To unsubscribe from this group, send email to dropio-api+...@googlegroups.com
> .
Reply all
Reply to author
Forward
0 new messages