Philipp Schweizer

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 23:04:39 +01:00

feat: tracker location based on multiple location providers

Hier habe ich Mist erzählt statt:

Pheanox suggested changes for localhorst/LocationHub#5

2025-01-01 23:04:39 +01:00

feat: tracker location based on multiple location providers

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 22:52:09 +01:00

feat: tracker location based on multiple location providers

await kann weg

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 22:52:09 +01:00

feat: tracker location based on multiple location providers

Der Wifi eintrag wird nur die die Datenbank geschrieben, wenn es eine Location gibt, sollte dieser nicht auch ohne reingeschrieben werden mit latitude und longitude undefined? Ansonsten würde ich es in drei steps unterteilen: Api Call, Datenbank entry erstellen, totalWeight + weightedLatitude + weightedLongitude ausrechnen. Ich glaube das macht es übersichtlicher ist aber vermutlich Geschmackssache. Mein Vorschlag:

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 22:52:09 +01:00

feat: tracker location based on multiple location providers

await kann weg

Pheanox suggested changes for localhorst/LocationHub#5

2025-01-01 22:52:09 +01:00

feat: tracker location based on multiple location providers

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 22:27:46 +01:00

feat: tracker location based on multiple location providers

await wifiScanService.createWifiScan

Pheanox commented on pull request localhorst/LocationHub#5

2025-01-01 22:13:58 +01:00

feat: tracker location based on multiple location providers

Ich hätte es so aufgebaut Vorschlag: Für jede Berechnung eine eigene Funktion die die Werte ausrechnet und dann zurück gibt `const CalculateTtngatewayLocation = (event: TtnMessageReceivedEven…

Pheanox deleted branch feat/webhook-endpoint from localhorst/LocationHub

2025-01-01 20:11:19 +01:00

Pheanox pushed to main at localhorst/LocationHub

2025-01-01 20:11:12 +01:00

210ebbb3e2 Merge pull request 'feat: wigle proxy call added' (#6) from feat/webhook-endpoint into main

a10a8d9d63 fix: added new env. varibales to template file

d8ec609baf feat: added cache version for api call

82296d0f2d feat: wigle proxy call added

Compare 4 commits »

Pheanox merged pull request localhorst/LocationHub#6

2025-01-01 20:11:11 +01:00

feat: wigle proxy call added

Pheanox pushed to feat/webhook-endpoint at localhorst/LocationHub

2025-01-01 19:33:16 +01:00

a10a8d9d63 fix: added new env. varibales to template file

Pheanox pushed to feat/webhook-endpoint at localhorst/LocationHub

2025-01-01 19:32:07 +01:00

d8ec609baf feat: added cache version for api call

Pheanox created pull request localhorst/LocationHub#6

2024-12-31 16:19:03 +01:00

feat: wigle proxy call added

Pheanox commented on pull request localhorst/LocationHub#5

2024-12-31 16:18:22 +01:00

feat: tracker location based on multiple location providers

Das ! kann weg.

Pheanox commented on pull request localhorst/LocationHub#5

2024-12-31 16:18:22 +01:00

feat: tracker location based on multiple location providers

Bzw. kann alles weg, wird nicht verwendet

Pheanox commented on pull request localhorst/LocationHub#5

2024-12-31 16:18:22 +01:00

feat: tracker location based on multiple location providers

Ich würde nach dem console.log ein return machen. Dann sparst du dir die else

Pheanox suggested changes for localhorst/LocationHub#5

2024-12-31 16:18:22 +01:00

feat: tracker location based on multiple location providers

Pheanox commented on pull request localhorst/LocationHub#5

2024-12-31 16:17:19 +01:00

feat: tracker location based on multiple location providers

Bzw. kann alles weg, wird nicht verwendet

Pheanox created branch feat/webhook-endpoint in localhorst/LocationHub

2024-12-31 16:14:10 +01:00