Associate "Code/Properties/Stuff" with Fields in C# without reflection. I am too indoctrinated by J

Posted by AlexH on Stack Overflow See other posts from Stack Overflow or by AlexH
Published on 2010-03-20T21:03:03Z Indexed on 2010/03/20 21:11 UTC
Read the original article Hit count: 276

Filed under:
|
|
|

I am building a library to automatically create forms for Objects in the project that I am working on.

The codebase is in C#, and essentially we have a HUGE number of different objects to store information about different things. If I send these objects to the client side as JSON, it is easy enough to programatically inspect them to generate a form for all of the properties.

The problem is that I want to be able to create a simple way of enforcing permissions and doing validation on the client side. It needs to be done on a field by field level.

In javascript I would do this by creating a parallel object structure, which had some sort of

{ permissions : "someLevel", validator : someFunction } 
object at the nodes. With empty nodes implying free permissions and universal validation. This would let me simply iterate over the new object and the permissions object, run the check, and deal with the result.

Because I am overfamilar with the hammer that is javascript, this is really the only way that I can see to deal with this problem. My first implementation thus uses reflection to let me treat objects as dictionaries, that can be programatically iterated over, and then I just have dictionaries of dictionaries of PermissionRule objects which can be compared with.

Very javascripty. Very awkward.

Is there some better way that I can do this? Essentially a way to associate a data set with each property, and then iterate over those properties.

Or else am I Doing It Wrong?

© Stack Overflow or respective owner

Related posts about c#

Related posts about reflection