CatchTheTornado / CatchTheTornado/text-extract-api

[feat] remove backward compatibility endpoints

Open
#99 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
3.2k
Forks
279
PR merge metrics
No merged PRs in 30d

Description

@choinek you generally just convinced me (after I've analyzed it for a while with the latest release) that keeping the backward compatibility forever is waste of energy and resources.

After we add the `extract` endpoint - let's keep the `ocr` endpoints as deprecated until the end of February max. Then, let's remove it.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the deprecated `ocr` endpoints and the newer `extract` endpoint in the repository, then review how endpoint removal is tested or documented. Confirm that `extract` is available before removing the backward-compatibility endpoints; done means the `ocr` endpoints are no longer exposed and existing supported behavior remains covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.