Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(developer/Upgrade_to_30): List all deprecations in detail #12081

Merged
merged 1 commit into from
Aug 1, 2024
Merged

docs(developer/Upgrade_to_30): List all deprecations in detail #12081

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 43 additions & 4 deletions developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_30.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,10 +179,49 @@ Deprecated APIs
- Calling ``OCP\DB\QueryBuilder\IQueryBuilder::update()`` with ``$alias`` is deprecated and will throw an exception in a future version as the underlying library is removing the functionality.
- Calling ``OCP\IDBConnection::getDatabasePlatform()`` is deprecated and will throw an exception in a future version as the underlying library is renaming and removing platforms which breaks the backwards-compatibility. Use ``getDatabaseProvider()`` instead.
- Calling ``OCP\Files\Lock\ILockManager::registerLockProvider()`` is deprecated and will be removed in the future. Use ``registerLazyLockProvider()`` instead.
- Using ``OCP\Translation`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead.
- Using ``OCP\SpeechToText`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead. Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead. Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead. Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\Translation`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\CouldNotTranslateException`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\IDetectLanguageProvider`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\ITranslationManager`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\ITranslationProvider`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\ITranslationProviderWithId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\ITranslationProviderWithUserId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\Translation\LanguageTuple`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`).
- Using ``OCP\SpeechToText`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\Events\AbstractTranscriptionEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\Events\TranscriptionFailedEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\Events\TranscriptionSuccessfulEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\ISpeechToTextManager`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\ISpeechToTextProvider`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\ISpeechToTextProviderWithId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\SpeechToText\ISpeechToTextProviderWithUserId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``SpeechToText`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Task`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\IProviderWithUserId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\IProvider`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\IManager`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Exception\TextToImageException`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Exception\TaskNotFoundException`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Exception\TaskFailureException`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Events\TaskSuccessfulEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Events\TaskFailedEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextToImage\Events\AbstractTextToImageEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextToImage`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\Events\AbstractTextProcessingEvent`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\Events\TaskFailedEvent`` is deprecated and will be removed in the future.Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\Events\TaskSuccessfulEvent`` is deprecated and will be removed in the future.Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\Exception\TaskFailureException`` is deprecated and will be removed in the future.Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\FreePromptTaskType`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\HeadlineTaskType`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\IManager`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\IProvider`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\IProviderWithExpectedRuntime`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\IProviderWithId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\IProviderWithUserId`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\ITaskType`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\SummaryTaskType`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\Task`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.
- Using ``OCP\TextProcessing\TopicsTaskType`` is deprecated and will be removed in the future. Use ``OCP\TaskProcessing`` instead (see :ref:`Task Processing<task_processing>`). Existing ``TextProcessing`` providers will continue to work with the TaskProcessing API until then.

Removed APIs
^^^^^^^^^^^^
Expand Down
Loading