Bug Fix: Entity ID Mismatch in Status Retrieval, unused params

[seanconrad1]

Summary
This PR fixes a bug related to inconsistent parameter usage when retrieving status by slug for single types in a Strapi integration. It aligns backend parameter names with what is sent from the frontend and removes unnecessary logic.

Changes
Renamed parameter from entityDocumentId to entityId in controllers.ts (getStatusBySlug()) and routes.ts (/get-status/:entityId) to match the frontend input.

Removed unused entityDocumentId when closing an entity — we now delete all items by entityId.

Removed unused entityId in getStatusByIdAndSlug() — lookup is handled via entityDocumentId and user.

Notes
No breaking changes or migrations.

No related issues — this was identified while integrating the package into a project.

Testing: Install the package into a Strapi project. The modal should now behave correctly and now pop up when two accounts access the same single type or collection type.

[Dan-Spector-NYO]

Hey @dominik-juriga @marek-fiala

@seanconrad1 and I were facing an issue where the record locking was not working in single types. This PR fixes that. If you have any questions, please let us know, and thank you in advance!!

[LeonGatt]

IMHO, it’s solid. Just one small nit regarding code style.
Could you, @dominik-juriga or @martincapek , please double check?

[LeonGatt]

Please change it to not duplicate code

await strapi.db.query("plugin::record-locking.open-entity").create({
  data: {
    user: String(userId),
    entityId,
    entityDocumentId: entityDocumentId,
    connectionId: socket.id,
    ...(entityDocumentId && { entityDocumentType }),
  },
});

[LeonGatt]

@seanconrad1 and @Dan-Spector-NYO Thanks a lot for helping us fix this open source plugin! And sorry for the late reply.