react components don't like compiling sass across multiple files. I'm exploring some resolutions, but right now including the nessie _init at the top of an individual component's scss file breaks the react compiler..

Mermaid is built with a different react structure https://github.com/sociomantic/plankton/tree/master/mermaid/chrome-react that @damian-rodriguez-sociomantic was able to style sassily without too much trouble.

we could also look into going the route facebook has gone, implementing a componentized, JS-ized, inline styling. If we're going to go full react in this case, maybe we go full facebook styling.
https://github.com/facebook/css-layout

@josh-wilson-sociomantic lets investigate further and decide on a path for this experimental tool that will hopefully yield some benefits to other mission critical projects at some point

If a request to the API failed(e.g. saving an event) the following should happen:

1. an failed request Action must be dispatched (important to contain cid(a unique client id) in the action payload)
2. The store will find the failed entity(most likely an event) with the help of the cid
3. The store will set a new property e.g. failedAPI to true.
4. A change event is triggered
5. App state is updated
6. Re-render of that event with a try again button which will attempt to send again to the api

The problem with the suggested approach above is, the user doesn't know why the request failed.
Hence it may be useful to introduce a new notifications or errors store which will also listen to any action which should in turn notify the user. Accordingly, a notifications component could render all notifications which haven't been read(read property which could be saved in the store)

Add a date picker and a date input.
Set the date by default to today.

Create the plus and minus buttons.

This looks like an interesting choice of date picker
http://zippyui.github.io/react-date-picker/

The missing date input and plus and minus buttons are in a different issue.

The button is to be titled 'Create and join'

Currently:

Wanted:

As in the example below:

The venue name needs to be pruned to ensure it fits inside the .event-box__header div

• The event header need to be sized correctly
• The font colour of the address is blue
• The venue name is black and the font size is smaller
• There's a separator between the time and the venue/address

Please report any bugs you found in the comments.

Current

http://www.wuala.com/sociomantic.com-ux/1.%20UI:UX/02_Design/Bacalao/Bacalao_2.jpg/

Wanted

• for the time being, the app has no date or search field at the top of the app, they may be implemented later, @amandine-orlowski-sociomantic can i just remove them for now and push up the main event section?
• the design is missing the 'new event' icon, currently signified by
  
  in the working app. @amandine-orlowski-sociomantic can you add this, bitte?

Implement yammer login in addition to Facebook.

Please leave feature requests in the comments

we need event time too :)

• Add 'Description' above the descrption.
• The avatars go on the right hand side.
• The avatars are circular
• Ensure the avatars have a size so it's not determined by the image size.
• Write how many places are left.
• style the number of places left(blue slightly bigger, red if one left) I can take care of adding the css classes if needed.

The design shows empty circles for places available. Please ignore this for now.
In the future we will hide some avatars if an event is attended by a large number of people.

Currently:
The client creating the event calls the createdEvent action creator twice (once for the HTTP request response and once for the event triggered by the socket and distributed to all).
The matching of information from the response is done based on the _id and cid.
The cid is an ID unique to the client and comes back in the HTTP response. The cid is omitted from the socket response because it's propagated to all connected clients.

The bug is that sometimes with the two responses there are as duplicate entries on the client side.