Somum.Entities.Enums 10.1.6

Somum.Entities.Enums

Somum.Entities.Enums is a .NET Standard 2.0 class library that centralizes the enumeration contracts shared by Somum domain projects.

It provides stable, strongly typed identifiers for domain concepts such as application settings, campaign and media states, filtering, object categories, user-defined data types, and access-control permissions.

Target Framework

• .NET Standard 2.0

The project can therefore be referenced by applications and libraries targeting .NET Standard 2.0 or a compatible later framework.

Contents

Domain enumerations

The root namespace, Somum.Entities.Enums, contains enums that describe common domain values:

Security enumerations

The Somum.Entities.Enums namespace defines the access-control vocabulary:

• enuSecureFunctionID identifies the securable function or feature area. Its values are module-oriented and bit-encoded.
• enuSecureRight defines the rights that can be granted for a function, from enu_sri_Deny through enu_sri_Full.

Use these enums together when storing, evaluating, or declaring permissions.

using Somum.Entities.Enums;

var function = enuSecureFunctionID.enu_sfi_UserProfile;
var requiredRight = enuSecureRight.enu_sri_Read;

User-defined field types

UserDefinedTypes identifies the type of a user-defined field. The selected enum value determines the compatible data representation and underlying storage column family, including general user-data and GIS/contact-data fields.

Examples include:

• enu_udt_Text
• enu_udt_Int
• enu_udt_DateTime
• enu_udt_Email
• enu_udt_List
• GIS address and coordinate types

Usage

Reference the project from another project in the solution:

<ItemGroup>
  <ProjectReference Include="..\Somum.Entities.Enums\Somum.Entities.Enums.csproj" />
</ItemGroup>

Then import the required namespace and use the enum values rather than persisted numeric literals:

using Somum.Entities.Enums;

var objectType = enuObjectType.enu_ot_UserProfile;

Compatibility and Versioning

Many enum values represent persisted or exchanged identifiers. Do not change existing numeric values or reuse retired values, because doing so can break database records, serialized payloads, permission evaluation, and integrations. Add new values deliberately and preserve the established naming and numeric-value conventions.

License

This project declares the MIT license expression in its project metadata.