plugin-entities

Manage custom data entities in the NeMo Platform by subclassing NemoEntity patterns and using the NemoEntitiesClient for persistent storage. This facilitates CRUD operations, cross-workspace filtering, and optimistic locking without manual database queries.

Optimistic locking for custom plugin entities in NeMo is handled automatically by the NemoEntitiesClient during CRUD operations. This prevents concurrent update conflicts by validating entity versions before persisting changes to the platform entity store.

Yes, you can perform filtered lookups of custom entities across different workspaces in NeMo. The NemoEntitiesClient supports cross-workspace filtering and pagination to retrieve plugin-specific data models efficiently.

You define custom entity models in the NeMo Platform by adhering to NemoEntity subclassing patterns and using the NemoEntitiesClient. FastAPI is utilized within the ecosystem, but entity storage relies on the platform's entity store.

The best way to handle CRUD operations for plugin-specific data models in NeMo is using the plugin-entities framework. It provides built-in support for creating, reading, updating, and deleting entities with automatic pagination and concurrency management.

Subclass NemoEntity when you need to define a custom data model, like a Widget entity, that integrates seamlessly with the NeMo Platform entity store. This standardizes validation and lifecycle management for your plugin-specific data.