Feat/bulk action component

[NoOne7135]

No description provided.

[Copilot]

Pull Request Overview

This PR introduces a new bulk action component system that allows attaching custom Vue components to actions. The main purpose is to enable custom wrappers around action triggers, such as requiring 2FA verification before executing actions.

Key changes:

• Adds support for customComponent property in action definitions
• Introduces CallActionWrapper component for handling action clicks
• Updates action handling across multiple views to support custom components

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
dev-demo/resources/users.ts	Updates user resource configuration to use new actions format and adds demo action
dev-demo/custom/ShadowLoginButton.vue	Adds new custom component file for testing
adminforth/types/Back.ts	Extends action interface to include optional customComponent property
adminforth/spa/src/views/ShowView.vue	Updates action button rendering to support custom components
adminforth/spa/src/components/ThreeDotsMenu.vue	Adds custom component support to dropdown menu actions
adminforth/spa/src/components/ResourceListTableVirtual.vue	Integrates custom components in virtual table action buttons
adminforth/spa/src/components/ResourceListTable.vue	Integrates custom components in regular table action buttons
adminforth/spa/src/components/CallActionWrapper.vue	New wrapper component for handling action clicks with disabled state
adminforth/modules/configValidator.ts	Adds validation for custom components in action definitions
adminforth/documentation/docs/tutorial/07-Plugins/02-TwoFactorsAuth.md	Documents how to use custom components with 2FA plugin

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The hardcoded 'extra' object with example data appears to be placeholder code that should be removed or made configurable.

Suggested change

	emit('callAction', extra);
	const props = defineProps<{ disabled?: boolean; extra?: any }>();
	const emit = defineEmits<{ (e: 'callAction', extra?: any ): void }>();
	function onClick() {
	if (props.disabled) return;
	emit('callAction', props.extra);

[Copilot]

Adding optional chaining (?.) to bulkActions suggests it might be undefined, but this could cause silent failures. Consider checking if bulkActions exists before filtering or provide a default empty array.

Suggested change

	<li v-for="action in bulkActions?.filter(a => a.showInThreeDotsDropdown)" :key="action.id">
	<li v-for="action in (bulkActions ?? []).filter(a => a.showInThreeDotsDropdown)" :key="action.id">

[Copilot]

[nitpick] The click handler uses both .stop and .prevent modifiers which might be overly restrictive. Consider if both are necessary or if this could interfere with expected event behavior.

Suggested change

	@click.stop.prevent="startCustomAction(action.id, row)"
	@click.stop="startCustomAction(action.id, row)"

[Copilot]

[nitpick] The click handler uses both .stop and .prevent modifiers which might be overly restrictive. Consider if both are necessary or if this could interfere with expected event behavior.

Suggested change

	@click.stop.prevent="startCustomAction(action.id, row)"
	@click.prevent="startCustomAction(action.id, row)"