Skip to content

Conversation

@haydenhoang
Copy link
Contributor

@haydenhoang haydenhoang commented Aug 30, 2024

Although Firestore support Geographical point data type, it is no longer recommended.

At this time we do not recommend using this data type due to querying limitations. It is generally better to store latitude and longitude as separate numeric fields. If your app needs simple distance-based geoqueries, see Geo queries

  • install dev dependency cross-env to run scripts and use a docker-compose.yml file to avoid The syntax of the command is incorrect. error on Windows
  • uninstall jest-dev-server and instead use Github actions services

- resolve typesense#84.
- feat: parse abbreviated field name `lat` & `lng`.
- parse object into geopoint type if object only contains `latitude`, `longitude` and `geohash` fields.
haydenhoang and others added 2 commits August 31, 2024 08:57
- use typesense v27.0 image
- add prettierrc
ci: fix parsing geopoint data type test
- use optional chaining to prevent error when accessing geopoint property
- configure eslint & prettier
- install `cross-env` to run scripts on Windows
- use a `docker-compose.yml` file to avoid `The syntax of the command is incorrect.` error on Windows
- uninstall `jest-dev-server` and instead use Github actions services
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Firebase Extension incorrect parsing of object[] into geopoint[]

2 participants