Revert "[NU-7164] Add basic parser for fragment input definitions (#7167)

[mslabek]

…167)"

This reverts commit d5154a3e7053d485fe766a021adee0401986411e.

Describe your changes

Checklist before merge

• [ ] Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• [ ] Code is cleaned from temporary changes and commented out lines
• [ ] Parts of the code that are not easy to understand are documented in the code
• [ ] Changes are covered by automated tests
• [ ] Showcase in dev-application.conf added to demonstrate the feature
• [ ] Documentation added or updated
• [ ] Added entry in Changelog.md describing the change from the perspective of a public distribution user
• [ ] Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• [ ] Verify that PR will be squashed during merge

Summary by CodeRabbit

• New Features

  • Streamlined type options logic in the Table and FragmentInputDefinition components.
  • Enhanced error handling in the ProcessValidator for improved validation outcomes.

• Bug Fixes

  • Simplified parameter validation processes in NodeCompiler and FragmentParameterValidator.

• Refactor

  • Removed unnecessary parameters and imports from various classes, including FragmentParametersDefinitionExtractor and FlinkProcessCompilerDataFactory.
  • Transitioned to static method calls for parameter validation, enhancing code clarity.

• Tests

  • Updated test cases to reflect changes in method calls and validation logic without altering expected outcomes.

[coderabbitai[bot]]

📝 Walkthrough

## Walkthrough The pull request introduces significant changes across multiple files, primarily focusing on the refactoring of how type options are managed within the application. In the `TableEditor.tsx`, the `useTableEditorTypeOptions` function is removed and replaced with the `useTypeOptions` hook, streamlining the retrieval of type options by eliminating Redux dependencies. Similarly, in `FragmentInputDefinition.tsx`, the `useFragmentInputDefinitionTypeOptions` function is updated to utilize the new `useTypeOptions` hook, enhancing consistency in type option management. In the server-side code, modifications to the `AlignedComponentsDefinitionProvider` involve adjusting parameters passed to the `FragmentComponentDefinitionExtractor`, indicating a refinement in data handling. Additional changes in test files enhance coverage and ensure correct behavior of component definitions and configurations. Overall, the changes simplify the instantiation of various components by removing unnecessary parameters and dependencies, while maintaining the core functionalities across the affected files. ## Possibly related PRs - **#7162**: The changes in this PR involve the modification of the `useTypeOptions` function to `useFragmentInputDefinitionTypeOptions`, which is related to the changes in the main PR that also involve the `useTypeOptions` hook in the `TableEditor.tsx` file. - **#7167**: This PR modifies the `useTypeOptions` function in the `FragmentInputDefinition.tsx` file, which is directly related to the changes in the main PR that involve the `useTypeOptions` hook in the `TableEditor.tsx` file. - **#7174**: This PR introduces the `TemplateEvaluationResult` class, which is relevant to the changes in the main PR that involve the handling of type options and template evaluations. - **#7183**: This PR includes changes that affect the visibility of categories in the UI, which may relate to the overall structure and functionality of components that handle type options and templates in the main PR. - **#7187**: This PR addresses issues related to node validation when using literal lists, which may connect to the changes in the main PR that simplify and streamline type handling in components. ## Suggested reviewers - arkadius

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.