CS should not always parse 'in' as a reserved word #2888

prajwalkman opened this Issue Mar 25, 2013 · 1 comment


None yet

2 participants


A problem arose in the Socket.io forums where
io.sockets.in('room').emit('event_name', data) wouldn't work because the in interpolation caused it to come out as
io.sockets["in"]('room').emit('event_name', data);
Source: socketio/socket.io#1191

Should CS ignore the in keyword if it is used as a parameter of an object? I don't think there's a use case where CS's in keyword is not surrounded by spaces.


I think you're talking about the missing brackets around the string. This is fixed as in 1.6.2.

@vendethiel vendethiel closed this Mar 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment