Skip to content
This repository was archived by the owner on Aug 28, 2025. It is now read-only.

feat : upsert sensor#232

Open
anshulchahar wants to merge 32 commits intodevfrom
feat/upsert_sensor
Open

feat : upsert sensor#232
anshulchahar wants to merge 32 commits intodevfrom
feat/upsert_sensor

Conversation

@anshulchahar
Copy link
Copy Markdown
Contributor

@anshulchahar anshulchahar commented Feb 20, 2025

  • Added a function to upsert the sensor.
  • Replaces the old Sensor information with the new if id is already found in the Database
  • Inserts a new sensor if id is not found in the Database
  • Editing of an existing sensor is currently not working and needs to be implemented

Needs: #231 and #235

@anshulchahar
Copy link
Copy Markdown
Contributor Author

Last 2 commits are new.
I have tested it, It works.

Comment thread src/actions/action_upsertSensor.ts Outdated
Comment thread src/components/mongodb/DBConnector.tsx Outdated
Comment thread src/models/zTinkerforgeSensor.schema.ts Outdated
Co-authored-by: Patrick Baus <patrick.baus@physik.tu-darmstadt.de>
@anshulchahar
Copy link
Copy Markdown
Contributor Author

anshulchahar commented Feb 20, 2025

There is some Textencoder error while running Tinkerforge schema test.
It was working before without a Problem ?

Comment thread src/components/mongodb/DBConnector.tsx
@anshulchahar anshulchahar marked this pull request as draft February 21, 2025 16:42
@anshulchahar anshulchahar marked this pull request as ready for review March 11, 2025 13:13
anshulchahar and others added 5 commits March 11, 2025 14:13
- added opportunity to add sensors in database
- a test for a component was removed because there was a problem with an environment variable that did not understand what it depended on (previously all tests passed).
@GGalya1 GGalya1 requested review from DaL31 and PatrickBaus March 20, 2025 15:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants