Why is ZohoAccount Sealed?

[DonMcNamara]

Hi,

Thanks for sharing this code! I'm just starting to use it and had a quick question.

Is there a reason that you sealed the entity classes? For example, I was thinking of inheriting from the ZohoAccount class to add some custom properties.

Thanks,
Don

[tsutomi]

Hi Don!

Thank you for taking in consideration using ZohoCrmSharp. Actually I sealed
the final entity classes for a conceptual reason, since they weren't
supposed to support polymorphism, and in fact you're the first person
asking me about this feature.
ZohoEntity in fact supports SetValue/GetValue methods for extending the
default properties and thus it is possible to extend their inherited
classes too.

You made a point by considering extending the "final" entities with custom
fields (like it is possible to create custom fields in Zoho CRM itself): I
will consider "unseal" them: for the moment the code is not very
maintained, cause I'm taken by clients' projects.

Cheers!

_Antonello Provenzano
_Consultant, Deveel IT Consulting and Services
+39 329 7357535 - [email protected]
http://www.deveel.com http://deveel.com

[image: Facebook] http://www.facebook.com/deveeldotcom [image:
Twitter]http://www.twitter.com/deveeldotcom [image:
LinkedIn] http://www.linkedin.com/company/deveel [image:
XING]https://www.xing.com/companies/deveel

On Wed, Jan 9, 2013 at 7:30 PM, DonMcNamara [email protected]:

Hi,

Thanks for sharing this code! I'm just starting to use it and had a quick
question.

Is there a reason that you sealed the entity classes? For example, I was
thinking of inheriting from the ZohoAccount class to add some custom
properties.

Thanks,
Don

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3.