Where should third-party Parser and ActionParser integrations live?

[CarloDotLog]

Hi team! 👋

I’m working on integrating third-party libraries into stac using custom ActionParsers and (widget) Parsers. For example:

• An ActionParser for sharing using share_plus
• A WidgetParser for rendering CachedNetworkImage
• A WidgetParser for displaying markdown content

I’m wondering what the preferred approach is for contributing these kinds of integrations.

Would you prefer:

1. Including them directly in the stac package, along with optional dependencies?
2. Or creating separate packages (e.g., stac_share_plus, stac_cached_network_image, stac_markdown), where each one depends on both stac and the third-party package?

The second option would keep the core lightweight and allow developers to opt in only to what they need, but I’d love to hear your thoughts before proceeding.

Let me know what direction you’d recommend. Thanks in advance!

[divyanshub024]

Hey @CarloDotLog 👋🏻

We should prefer the second option. As you said, the core library needs to stay lightweight.

A parser package may not have to depend upon stac package. It can simply use the stac_framework package.

We also have a third-party parser implementation for flutter_webview. You can check that out as well.