Allow legacy orchestration

Walkthrough

The changes in this pull request involve updates to the OperatorExecutionOption type and the useOperatorPromptSubmitOptions function in state.ts, allowing for more flexible description types and making the onClick method optional. Documentation has been enhanced to include a new environment variable, FIFTYONE_ALLOW_LEGACY_ORCHESTRATORS, and a configuration field, allow_legacy_orchestrators, for managing legacy orchestrators. Additionally, the ExecutionOptions class now dynamically determines orchestrator registration based on the new configuration. Minor UI improvements were made to the SplitButton component.

Changes

File	Change Summary
app/packages/operators/src/state.ts	Updated `OperatorExecutionOption` type: `description` accepts `string \| React.ReactNode`, `onClick` is optional. Updated "Schedule" description. Imported new Markdown component for warning message. Fixed typo in variable name.
docs/source/plugins/using_plugins.rst	Added section on `FIFTYONE_ALLOW_LEGACY_ORCHESTRATORS` for managing legacy orchestrators. Enhanced plugin management instructions.
docs/source/user_guide/config.rst	Added `allow_legacy_orchestrators` configuration field (default `False`). Updated configuration viewing instructions and examples.
fiftyone/core/config.py	Added `allow_legacy_orchestrators` attribute to `FiftyOneConfig`, initialized from input dictionary.
fiftyone/operators/executor.py	Updated `orchestrator_registration_enabled` property to return dynamic value based on `allow_legacy_orchestrators`.
app/packages/operators/src/SplitButton.tsx	Added `sx` prop to `MenuItem` for conditional cursor styling based on `option.onClick`. Updated `PrimaryWithTag` function to include `disabled` parameter.
docs/source/plugins/developing_plugins.rst	Enhanced clarity and comprehensiveness of the plugin development guide. Added new examples and sections.

Possibly related PRs

#4557: The changes in the main PR regarding the OperatorExecutionOption type and the useOperatorPromptSubmitOptions function may relate to the DashboardView component, which involves managing dynamic layouts and user interactions, potentially utilizing similar execution options.
#4785: The updates to the documentation regarding environment variables for the plugin orchestrator may connect to the changes in the main PR that involve execution options, as both deal with orchestrating operations within the application.
#4850: The enhancements to group slice support in operators could relate to the changes in the main PR, as both involve modifications to how execution options and context are managed within the application.
#4902: The addition of spaces context to operators aligns with the changes in the main PR, which also deals with execution options and context management, enhancing the overall functionality of operator execution.
#5111: The change to always disable orchestrator registration may relate to the main PR's focus on execution options, as both involve aspects of how operations are managed within the application.
#5140: The documentation updates regarding the builtin orchestrator may connect to the main PR's changes, as both involve clarifying how operations and execution contexts are handled within the application.

Suggested labels

documentation

Suggested reviewers

ritch
swheaton

🐰 In the code, we hop and play,
With options new, we pave the way.
Legacy orchestrators now take flight,
In FiftyOne's realm, all feels just right!
With buttons split and styles so neat,
Our changes make the app a treat! 🥕

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. ### 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.

voxel51 / fiftyone