feat: add validation hooks to surface prerequisites for installation mutations

[dionlow]

Summary

• Add useInstallationValidation hook that exposes clear validation states
• Update mutation hooks to expose canCreate, canUpdate, canDelete flags
• Provide detailed validationErrors object for better developer experience

Changes

• New hook: useInstallationValidation - centralized validation logic

  • Returns canCreate, canUpdate, canDelete boolean flags
  • Returns validationErrors object with detailed error states
  • Returns current installation and integrationObj for convenience

• Updated hooks:

  • useCreateInstallation - now exports canCreate and validationErrors
  • useUpdateInstallation - now exports canUpdate and validationErrors
  • useDeleteInstallation - now exports canDelete and validationErrors

Why

Previously, developers had to call mutation functions to discover validation errors. Now validation state is exposed upfront, allowing:

• UI to disable buttons when operations aren't valid
• Display helpful messages about what's missing
• Check prerequisites before attempting mutations
• Better developer experience with clearer error states

Example Usage

const { createInstallation, canCreate, validationErrors } = useCreateInstallation();

// Check if creation is possible
if (!canCreate) {
  if (validationErrors.installationExists) {
    console.log("Installation already exists");
  }
  if (validationErrors.noIntegration) {
    console.log("No integration found");
  }
}

// Disable button in UI
<button disabled={!canCreate} onClick={handleCreate}>Create</button>

[Copilot]

Pull Request Overview

This PR adds upfront validation capabilities to installation mutation hooks, allowing developers to check prerequisites before attempting operations. Previously, validation errors were only discoverable after calling mutation functions.

Key Changes:

• Introduced useInstallationValidation hook for centralized validation logic
• Enhanced mutation hooks (useCreateInstallation, useUpdateInstallation, useDeleteInstallation) to expose validation state
• Added public export of the new validation hook

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/headless/installation/useInstallationValidation.ts	New hook providing validation flags and detailed error states for installation operations
src/headless/installation/useCreateInstallation.ts	Enhanced to expose canCreate and validationErrors from validation hook
src/headless/installation/useUpdateInstallation.ts	Enhanced to expose canUpdate and validationErrors from validation hook
src/headless/installation/useDeleteInstallation.ts	Enhanced to expose canDelete and validationErrors from validation hook
src/headless/index.ts	Added public export for useInstallationValidation

---

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

[Copilot]

The useInstallationValidation hook internally calls useIntegrationQuery and useInstallation, resulting in duplicate hook calls since these are already invoked on lines 25-26. This creates redundant queries and state management. Consider refactoring useInstallationValidation to accept integrationObj and installation as parameters to avoid duplicate hook invocations.

Suggested change

	const { canDelete, validationErrors } = useInstallationValidation();
	const { canDelete, validationErrors } = useInstallationValidation(integrationObj, installation);

[Copilot]

The useInstallationValidation hook internally calls useIntegrationQuery and useInstallation, resulting in duplicate hook calls since these are already invoked on lines 31-32. This creates redundant queries and state management. Consider refactoring useInstallationValidation to accept integrationObj and installation as parameters to avoid duplicate hook invocations.

Suggested change

	const { canUpdate, validationErrors } = useInstallationValidation();
	const { canUpdate, validationErrors } = useInstallationValidation(integrationObj, installation);

[Copilot]

The useInstallationValidation hook internally calls useIntegrationQuery and useInstallation, resulting in duplicate hook calls since these are already invoked on lines 32 and 34. This creates redundant queries and state management. Consider refactoring useInstallationValidation to accept integrationObj and installation as parameters to avoid duplicate hook invocations.

Suggested change

	const { canCreate, validationErrors } = useInstallationValidation();
	const { canCreate, validationErrors } = useInstallationValidation(integrationObj, installation);