Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to settle on payload structure #22

Open
mikemimik opened this issue Dec 4, 2016 · 0 comments
Open

Need to settle on payload structure #22

mikemimik opened this issue Dec 4, 2016 · 0 comments

Comments

@mikemimik
Copy link
Owner

Need to decide what the structure of the payload for the widget should look like.

Proposed:

{
    "id": int,
    "title": String,
    "url": String,
    "date_start": DateTime,
    "date_end": DateTime,
    "details": Object
}

Rational:

The title, date_start, and date_end are the bare minimum for the widget to be useful. The url gives the widget a location to get details about this particular event, could be used for future plans. The details property is by far the most useful. Since it's an object, it gives the user the ability to bury whatever data they want into each event. They could then extend the widget to utilizes these things.

@mikemimik mikemimik added this to the Serviceable milestone Dec 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant