Form Questions Manager + Update Form Tool #68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced CreateFormTool to facilitate form creation. - Added createForm GraphQL mutation to handle form creation requests. - Updated package.json to include @mondaydotcomorg/workforms-contracts dependency. - Enhanced GraphQL types to support the new mutation.
- Added comments to clarify the purpose of the WorkForms operations section. - Introduced createForm mutation for creating new monday forms (API version 2025-10).
- Introduced GetFormTool for fetching forms by token. - Added getForm GraphQL query to retrieve detailed form information. - Updated GraphQL types to include GetFormQuery and its variables.
…ndencies - Deleted CreateFormTool and GetFormTool as part of the refactor. - Removed @mondaydotcomorg/workforms-contracts dependency from package.json. - Updated import paths for GraphQL types to reflect new structure.
- Moved CreateFormTool and GetFormTool imports to the workforms-tools directory. - Cleaned up import statements to reflect the new structure.
- Updated import paths for CreateFormTool and GetFormTool to reflect their new location in the workforms-tools directory. - Ensured all relevant tools are correctly exported from the updated structure.
- Added documentation for CreateFormTool and GetFormTool under WorkForms Operations section. - Enhanced clarity on the toolkit's capabilities for managing forms in monday.com.
- Changed import paths for CreateFormTool and GetFormTool to use the new workforms.graphql file. - Removed the old queries.graphql file references to streamline the codebase.
- Introduced mutations for creating, updating, and deleting form questions in the GraphQL API. - Updated the Form interface to include operations for managing questions. - Enhanced GraphQL types to support new question management functionalities. - Added FormQuestionsEditorTool to facilitate question editing within forms.
- Consolidated form tool schemas into a dedicated file for better organization. - Updated CreateFormTool, FormQuestionsEditorTool, and GetFormTool to utilize the new schema imports. - Enhanced the FormQuestionsEditorTool to improve variable handling during question operations. - Corrected GraphQL description labels for clarity in form question types.
- Added an optional title field to the base question schema for improved flexibility. - Simplified the createQuestionSchema by removing the validation function, streamlining the schema definition. - Updated the formQuestionsEditorToolSchema to reference the baseQuestionSchema for question updates.
- Added an optional title field to the base question schema for improved flexibility. - Simplified the create and update question schemas by removing redundant title definitions. - Updated the formQuestionsEditorToolSchema to reference the base question schema directly for question updates.
…alidation and schema updates - Updated the formQuestionsEditorToolSchema to include optional questionId and question fields for better flexibility. - Enhanced validation for create, update, and delete operations to ensure required fields are provided. - Improved GraphQL descriptions to clarify requirements for question operations. - Refactored input handling in FormQuestionsEditorTool to streamline question management processes.
…or improved type handling - Refactored FormQuestionsEditorTool to utilize specific input and output types based on formQuestionsEditorToolSchema. - Updated import paths for GraphQL types to reflect the new directory structure. - Enhanced getInputSchema method to return the correct schema type, improving type safety and clarity.
…perations - Updated mutation names for creating and updating form questions to follow a consistent naming convention. - Changed `create_question` to `create_form_question` and `update_question` to `update_form_question` for clarity and alignment with other operations.
…ttings - Eliminated the labelLimitCount field from the form question settings in GraphQL schemas and related files. - Updated GraphQL descriptions to clarify the requirements for select-type questions. - Adjusted the question schema and GraphQL operations to reflect the removal of this field, streamlining the question management process.
… questions - Updated the description for selectOptions in GraphQL to enhance clarity on when options are required for creating select-type questions. - Ensured consistency in language to improve understanding of the question creation process.
GuyHadas
changed the title
- Introduced UpdateFormTool to facilitate form updates, including title, description, and question management. - Added GraphQL mutations for updating form properties and settings, enhancing the toolkit's capabilities for form management. - Updated schemas and types to support the new update operations, ensuring consistency and clarity in the API. - Enhanced GraphQL descriptions to provide detailed information on the new update functionalities.
…nused fields - Consolidated and clarified GraphQL descriptions for various query and mutation types to enhance readability and understanding. - Removed the `labelLimitCount` field from the `FormQuestionSettings` type, simplifying the schema and focusing on essential properties. - Updated related GraphQL schemas and types to ensure consistency and clarity across the toolkit.
…for clarity and consistency - Renamed `FormQuestionsOperation` to `FormQuestionActions` for improved clarity in action handling. - Updated the `formQuestionsEditorToolSchema` to reflect the new action naming and enhance type safety. - Enhanced GraphQL descriptions to include new actions for form updates, including tag management and question operations. - Streamlined the `UpdateFormTool` to support various form update actions, improving overall functionality and user experience.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://monday.monday.com/boards/3709356818/pulses/9834449679
Implements the Form Questions Manager tool for creating/updating/deleting form questions