Separate Project for Search-a-licious Dart SDK with Integration in OpenFoodFacts-Dart

[teolemon]

Why - Problem Description

• As part of the search-a-licious project funded by NGI Search, we need a distinct Flutter SDK for search-a-licious. Contrary to the current implementation of search on the OFF Dart SDK, this SDK needs not to be tightly integrated with Open Food Facts but instead be re-usable by other projects.

What - Proposed Solution

• The creation of a separate folder in the Search-a-licious repository with a dedicated search-a-licious Dart SDK. This SDK will focus solely on providing search API feature and widgets. The OpenFoodFacts-Dart project should then integrate this SDK, utilizing its search capabilities with specific parameters.

Additional Context

• This separation will require setting up a new repository for the Search-a-licious Dart SDK.
• The SDK should have its own deployment pipeline to pub.dev, ensuring independent releases without Open Food Facts specific configs.
• The integration with OpenFoodFacts-Dart should be done in a way that seamlessly replaces the current next-gen search functionalities (fortunately nothing much at the moment beyond autocomplete) with those provided by the Search-a-licious Dart SDK.

[monsieurtanuki]

this SDK needs not to be tightly integrated with Open Food Facts but instead be re-usable by other projects.

My 2 cents: in that specific case I cannot see the point of a dart library if it's not tightly integrated with OFF.
The only point of the library is to get - let's say - a Product.
If the point of the library is just to build a GET and get a JSON without decoding it, the interest is quite limited.
That said, I don't know that much about Search-a-licious.