Identify Show First Control

On map click, identifies the first hit and runs the identify resolver (default: show-detail / attribute-table when available). No toolbar button. Needs identify nodes on the dataset (see Identify).

Abort policy (same as Identify session): each click aborts the previous in-flight runIdentifyShowFirst via AbortController and passes a new requestId. A newer click wins; aborted runs do not update the result panel. Unmount aborts and clears loading.

Hit UI follows each identify node’s onSingle / onMultiple (see IdentifyControl resolver). Mount IdentifyControl / result panel when the policy opens the result panel.

Props

Prop	Description	Type	Required	Default Value
mapId		string	false	--
dragId		string	false	--
btnWidth		number	false	40
controlOrder	CSS flex order for the standalone button	number	false	0
position		'top-left', 'top-right', 'bottom-left', 'bottom-right'	false	'bottom-right'
controlLayout	'standalone' (corner), 'toolbar' (always in toolbar), 'button' (always corner; not auto-promoted on mobile)	'standalone' | 'toolbar' | 'button'	false	'standalone'
controlVisible		boolean	false	true

Map also accepts buttonInMobile ('button' | 'toolbar' | 'menu', default 'button'). On viewports ≤640px:

• 'button' — leave corner buttons unchanged
• 'toolbar' — move declared control buttons into a single ToolbarControl host (except controlLayout="button"). Mount one ToolbarControl in the map slot
• 'menu' — hide per-control corner buttons; fan out intact clusters by position into corner stacks with outside-in More. Mount one ToolbarControl.

See ToolbarControl.

No control-specific props beyond shared map props.

Events: none.

Vue

<script setup lang="ts">
import { Map } from '@hungpvq/vue-map-core';
import { IdentifyShowFirstControl, ComponentManagementControl } from '@hungpvq/vue-map-dataset';
</script>

<template>
  <Map>
    <IdentifyShowFirstControl />
    <ComponentManagementControl />
  </Map>
</template>

React

<IdentifyShowFirstControl />
<ComponentManagementControl />