Closed
Bug 874292
Opened 12 years ago
Closed 12 years ago
Validate POST request body for event creation
Categories
(Webmaker Graveyard :: Events, defect)
Webmaker Graveyard
Events
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hike, Assigned: hike)
References
Details
(Whiteboard: s=2013w22)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31
Steps to reproduce:
curl -X POST -H 'Content-Type: application/json' -d '{
"title": "...",
"description": "...",
"address": "...",
"begins": "...",
"ends": "...",
"resource": "...",
"organizer": "...",
"image": "..."
}' <server>/events
Expected results:
Validate fields;
- if event is valid, create event and return Event object in json or html 'Details' page depending on Accept-header or uri extension (.json)
- otherwise, return error message in html or json
Updated•12 years ago
|
Whiteboard: s=2013w21
* Upon creating an event we currently ask a user for the start time and end time. If the event spans multiple days, how does a time come into play? Does that signify the daily event times? To help clarify the question, refer to the mockup's event details page. How would a user know to specify that the start date is September 30 at 11am and ending on October 31 at 5pm? What does that even mean?
Comment 2•12 years ago
|
||
I think it will end up being highly dependent on the event. In most cases, if something is a multi-day drop-in sort of thing (like: this hackerspace will be open) then people will use it as the open/close times for those spaces.
In some cases it will be irrelevant, but I think the user will just deal with that.
Updated•12 years ago
|
Whiteboard: s=2013w21 → s=2013w22
Event-creation is now implemented, but currently without field validation. I'll make a separate ticket for client-side form validation.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Summary: Allow Event creation with field validation. → Validate POST request body for event creation
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•