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.

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

Improve backend resolution logic #802

Open
vagenas opened this issue Jan 24, 2025 · 0 comments
Open

Improve backend resolution logic #802

vagenas opened this issue Jan 24, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@vagenas
Copy link
Contributor

vagenas commented Jan 24, 2025

Requested feature

Document conversion currently contains a logic for "guessing" / resolving the backend to use for a given input (ref).

This logic has some limitations, e.g. when working with streams, it relies on the first 8KB to detect the backend to use — which may or may not be enough for a correct detection (e.g. deciding info could only appear at the end of a 10KB stream).

Consider ways to remove these limitations.

One possible high-level approach to examine could be to:

  • remove the current layer of "guessing" a backend a priori and then committing to that guess, and
  • instead, keep for each format, e.g. XML, a list of backends to try one after another, until one successfully parses (can have a default list, parametrizable by the user).
@vagenas vagenas added the enhancement New feature or request label Jan 24, 2025
@vagenas vagenas changed the title Improve backend resolution Improve backend resolution logic Jan 24, 2025
@vagenas vagenas assigned vagenas and unassigned vagenas Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant