Hey, I have installed the extension and using the official Typesense cloud to host but I am getting this error from the firebase cloud function when creating new documents:

Flutter Web/ Dart code:

@override
void initState() {
  const host1 = "wt62ejrukzvh378pp-1.a1.typesense.net";
  const host2 = "wt62ejrukzvh378pp-2.a1.typesense.net";
  const host3 = "wt62ejrukzvh378pp-3.a1.typesense.net";
  const protocol = Protocol.http;
  final config = Configuration(
    // Replace with your configuration
    '[admin key (removed on github for security reasons)]',
    nodes: {
      Node(
        protocol,
        host1,
        port: 443,
      ),
      Node(
         protocol,
        host2,
        port: 443,
      ),
      Node(
        protocol,
        host3,
        port: 443,
      ),
    },
    numRetries: 3, // A total of 4 tries (1 original try + 3 retries)
    connectionTimeout: const Duration(seconds: 10),
  );
  client = Client(config);

  super.initState();
}

Below are the screenshots for the extension configuration and firebase functions log:

As far as I've understood from gazing at the implementation in JavaScript and Python, here are the requirements summed up:

The main function is the make_request or equivalent. It's responsible for connecting with a node and completing the request. If a nearestNode is present in the Configuration, it'll try to connect to it given it's healthy, if not it'll fall back to the nodes and use them in a round-robin fashion.

I'm not sure how if a node is healthy is tracked? What I think: Every node starts with their health status as "fine" and when eventually if a request fails, that node is marked unhealthy and the next node is tried until eventually due to round-robin this node is considered again, and if the request is successful this time, it's again marked healthy again? Also, is this where numRetries comes into play? In that, if a node fails to respond, we would try the same node numRetries times?

I'm also not sure about healthcheckInterval present in the Configuration class. What's its use?

Describe the bug

It seems the Configuration object is not setting the API key. Basic configuration:

class SearchService {
Client? client;
String searchOne = "add-endpoint-here";
String searchTwo = "add-endpoint-here";
String searchThree = "add-endpoint-here";

void initialize(String searchKey) {
    var config = Configuration(
      searchKey,
      nodes: {
        Node(Protocol.https, searchOne, port: 443),
        Node(Protocol.https, searchTwo, port: 443),
        Node(Protocol.https, searchThree, port: 443),
        },
      connectionTimeout: Duration(seconds: 2),
      );
      client = Client(config);
   }

  Future<dynamic> Search(
    String? value,
    String queryBy,
    String collection,
  ) async {
    try {
      var search = await client!.collection(collection).documents.search({
        "q": value ?? "*",
        "query_by": queryBy,
      });
         return search;
        } catch(err){
          return err;
        }
    }
}

Related: Typesense Error 476

Steps to reproduce the behavior:

1. Initialize client - No issues
2. Search/retrieve documents - Error

Expected behavior

1 . Return either collections or documents.

Additional context

• Using a shell to query/retrieve any document doesn't cause any issue.
• Using Admin-Key, Search-only-Key, and Scoped-Key cause the same errors.
• Using client SDK:

Error 1

401: {"message": "Forbidden - a valid `x-typesense-api-key` header must be sent."}

Error 2 This error is also a weird behavior from the client SDK. All schema variables are defined with type and facet. If the client is not throwing Error 1, it's giving this other error:

400: {"message": "Field `value` should be a string or a string array."}

"value" variable config (Schema):

...
    {
      "facet": false,
      "index": true,
      "name": "value",
      "optional": false,
      "type": "float"
    },
...

Note: Setting the "sendApiKeyAsQueryParam" variable won't change the outcome.

Description

According to the docs

You can — and should — migrate your package before packages that depend on it are migrated. Your null-safe package is usable by packages and apps that don’t use null safety yet, as long as they use Dart 2.12 or later. For example, the Dart and Flutter core libraries are null safe, and they’re still usable by apps that haven’t migrated to null safety.

Since it's encouraged to be in Dart 2.12 or later, we'll update the dart client.

I can assign a locale to a schema field using the API directly, like this

	 curl "http://localhost:8108/collections" \
       -X POST \
       -H "Content-Type: application/json" \
       -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
       -d '{
         "name": "english_thai",
         "fields": [
          {"name": "english", "type": "string" },
          {"name": "thai", "type": "string", "locale": "th" }
         ],
         "default_sorting_field": "num_employees"
       }'

I can't find an equivalent way to specify locale using the dart client.

Can you please explain how I can make a simple search on one of my collections? I followed the typesense tutorials but I can't get anything to work with your package. Thanks

Thank you very much @happy-san for the amazing work on the Dart client.

Is your feature request related to a problem? Please describe.

Typesense 0.21 introduces geo search so you can index and search on lat/long fields. A new type geopoint is introduced for this purpose.

Please see usage here: https://gist.github.com/kishorenc/1f537c728f89960048272a03d36bad01

Describe the solution you'd like

• [x] #91

• [x] #92

Is your feature request related to a problem? Please describe.

In the next version of Typesense (0.23) we're supporting in-place schema changes to collections through a PATCH /collections/:name end-point. We need to add this method to the client.

Describe the solution you'd like

Please see the examples I've created for the various clients (not all of them are implemented yet) here.

The Dart version looks like this:

final updateSchema = UpdateSchema(
  {
    Field('company_category', Type.string),
    Field('num_employees', drop: true)
  }
);
await client.collection('companies').update(updateSchema);

For now you can change only the fields (can't change the name or other properties like default_sorting_field etc. yet). So we need a UpdateSchema wrapper class that's a subset of the Schema class (only containing fields) with which we can call the .update().

cc @happy-san

Is your feature request related to a problem? Please describe.

I miss the known type safety by missing models for SearchParameters and SearchResponse, a map is always not as easy to use and more error prone than a model.

Describe the solution you'd like

Add the models for SearchParameters and SearchResponse.

Is your feature request related to a problem? Please describe.

_cachedResponses doesn't have a limit on the number of _Cache's it can store and the expired _Cache is conditionally deleted, so a memory leak occurs.

Describe the solution you'd like

Implement an LRU algorithm.

Additional context

related issue

Is your feature request related to a problem? Please describe.

Currently, the codecov badge in README isn't connected to CI and shows Unknown status

Describe the solution you'd like

Get it working by integrating uploading coverage reports in the CircleCi workflow.

Describe alternatives you've considered

Well many, just couldn't get it working.

Additional context