Detect Document Identifiers in the JSON View

Detect Document Identifiers in the JSON View

This feature aims to enhance the JSON View by detecting _id and other configurable identifiers (such as partition key values for Cosmos DB NoSQL) from a selected document. Since different databases use varying sets of identifiers, this functionality will be configurable to adapt to specific database requirements. The feature will enable contextual operations on selected data within the JSON View.

Core Functionality

1. Configurable Identifier Detection

   • Allow configuration of identifier types to accommodate different databases:
     • Default to detecting _id for MongoDB.
     • Support additional identifiers, such as partition keys for Cosmos DB NoSQL or other database-specific fields.

2. Support for Various Selection Scenarios

   • Cursor Position Only: When no selection is made, determine the closest enclosing document based on the cursor position.
   • Partial Selection: Identify if the selected text falls within a document and extract the relevant identifiers.
   • Multiple Document Selection: Handle cases where multiple documents are selected, extracting identifiers for all detected documents.

3. Enable Contextual Operations

   • Use the detected identifiers to enable operations on the selected data, such as:
     • Highlighting related entries in other views.
     • Performing targeted updates or deletions.
     • Enabling navigation to related documents or collections.

No files, tests, or entry points are named. Start by locating the JSON View implementation and its selection-handling code, then identify where database-specific identifier configuration belongs. Done means supporting cursor, partial, and multiple-document selections with configurable identifiers for contextual operations.