This project is read-only.

How can I Opt out of Clay in certain instances?

Topics: Core, Troubleshooting, Writing modules
Feb 4, 2013 at 10:06 PM
Edited Feb 5, 2013 at 9:14 AM
Hey All,

Okay so I am having the problem with a line of code like this..

// This line returns a Dynamic object
var group = Clients.Group(contentGroupName);
// This line should do something dynamic-y to it, it has nothing to do with Clay, however calling addUser on group throws a // MathodNotImplemented exception within Clay...
var addeduserGroup = group.addUser(user, contentGroupName, isUserOwner);

group is a SignalRProxy object, which is cast as Dynamic under the hood, I am not using Clay anywhere within this code, but for some reason Clay is attaching to it.

How can I opt out of Clay?

Feb 10, 2013 at 8:13 AM
That doesn't make any sense. You must be missing something, but it's impossible to say with that little information. Clay does not magically attach itself to any dynamic.
Feb 10, 2013 at 10:46 AM
I know it doesn't make sense, but it was... weird huh! I have pulled the Clayless branch and it has gone away...