parseError

[smilansky]

I am getting the following error when trying to create an event like this:

    calendar.create_event do |e|
      e.title = "Initial consultation with #{params[:name]}"
      e.location = "Skype handle - #{params[:skype]}"
      e.description = "#{params[:name]} requested an appointment: 
      \nPhone Number: #{params[:phone_number]}
      Email: #{params[:email]}  
      Notes: #{params[:notes]}"
      e.start_time = appointment_time
      e.end_time = appointment_time + (30 * 60)
    end 

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "parseError",
    "message": "Parse Error"
   }
  ],
  "code": 400,
  "message": "Parse Error"
 }
}

I don't get the error when I omit the description and location fields. Did the API change the way they parse strings?

[szich]

Yep, we switched from Nokogiri to Json. What are the value of params[:slype] and params[:name]?

[smilansky]

They are '1' and '1', but were failing on other values too. I isolated the error to the description - when I stripped description from the event creation, it always created the event.

[szich]

JSON like newlines as either \n or \r\n for *nix or windows respectively.

This works:

params = {}
params[:name] = '1'
params[:skype] = '1'
params[:phone_number] = '1-800.555.1212'
params[:email] = '[email protected]'
params[:notes] = 'These are some notes.'
appointment_time = Time.now

event = gc.create_event do |e|
  e.title = "Initial consultation with #{params[:name]}"
  e.location = "Skype handle - #{params[:skype]}"
  e.description = "#{params[:name]} requested an appointment: \\nPhone Number: #{params[:phone_number]} \\nEmail: #{params[:email]}  \\nNotes: #{params[:notes]}"
  e.start_time = appointment_time
  e.end_time = appointment_time + (30 * 60)
end 

puts event

I would like to improve our parsing so it does this conversion automatically. However, I don't have time to implement a fix right now. if this is something you need immediately it would be great if you could submit a pull request.

[mrjcleaver]

Looks like what I just did in #81

[szich]

I'm closing this issue as #81 more correctly describes the issue.