- Introduced `menu.json` for menu component structure with bindings for trigger and content.
- Created `password-input.json` for password input handling visibility and value changes.
- Added `popover.json` for popover component with trigger and content bindings.
feat: Implement custom hooks for UI interactions
- Added `useAccordion` for managing accordion state with single/multiple item support.
- Created `useBindingEditor` for managing bindings in a dynamic editor.
- Implemented `useCopyState` for clipboard copy functionality with feedback.
- Developed `useFileUpload` for handling file uploads with drag-and-drop support.
- Introduced `useFocusState` for managing focus state in components.
- Created `useImageState` for handling image loading and error states.
- Added `useMenuState` for managing menu interactions and item clicks.
- Implemented `usePasswordVisibility` for toggling password visibility.
- Developed `usePopoverState` for managing popover visibility and interactions.
feat: Add constants and interfaces for JSON UI components
- Introduced constants for sizes, placements, styles, and object-fit handling.
- Created interfaces for various components including Accordion, Binding Editor, Copy Button, Data Source Editor, File Upload, and more.
- Added type definitions for menu items, popover props, and other UI elements to enhance type safety and maintainability.
Please find a solution for this failing job. Use the logs, job definition, and any referenced files where the failure occurred. Keep your response focused on the solution and include code suggestions when appropriate.
1 reference
The job failed because your package-lock.json file is not in sync with package.json. Specific issues from the logs include:
The lock file has @github/spark@0.0.1 but package.json asks for @github/spark@0.44.15.
Several dependencies (like octokit and its plugins) are required by package.json but missing from the lock file.
Solution:
On your local machine, run:
Code
npm install
This will update your package-lock.json to match your current package.json.
Commit both package.json and the updated package-lock.json, then push the changes to your repository.
Re-run the workflow.
This will ensure npm ci works as expected and resolves the lock file errors. If you have multiple contributors, make sure everyone uses the updated files to avoid future sync issues.
