seamapi/fake-seam-connect

Fake for Seam Connect.

fake-seam-connect's Issues

Add /_fake/seed

Returns the seed object if the db is seeded, otherwise returns null (or status code?)

Introduce a mutable server for fake-seam-connect

e.g. either of the following schemes are good:

• https://<mutable_ref>.fake-seam-connect.com/...
• https://fake-seam-connect.seam.co/<mutable_ref>/...

Using headers is an interesting approach as well but I think it's too subtle and could cause confusion.

I was initially against a mutable server, instead preferring in-browser fakes or "dynamically spun up" instances. I think the Pros of having it available have outweighed the Cons to me:

Pros

• Very simple to set up fixturing, just change the endpoint
• SDK tests are made dramatically easier because there is no testcontainers required

Cons

• Tests are always coupled to the latest seam connect
• Seeing logs or debugging seam connect state is much more difficult, sometimes not possible

Simple fake sandbox implementation using postgres: https://github.com/seamapi/unified-access-services/blob/main/apps/temporary-api/pages/api/nightly/%5B...uas_path%5D.ts

/internal/phone/user_identities/(list_endpoints|prepare_endpoint)

`/locks/unlock_door` doesn't work in sdk testing

import Seam from "seamapi"

const seam = new Seam({
  endpoint: `https://r${Math.random()
    .toString(16)
    .slice(2)}.fakeseamconnect.seam.vc`,
  apiKey: "seam_apikey1_token",
})


console.log(
  await seam.locks.unlockDoor("august_device_1")
)

Support `POST` on `/health` endpoint

Implement `/workspaces/create`

As implemented here: https://github.com/seamapi/seam-connect/pull/4935

Fake server returns 404 for /openapi.json

ID generation creating duplicate ids

Support personal access tokens

See also seamapi/nextlove#124 and #124

Phone fake seam connect implementation

Epic for fake seam connect endpoints that need to be implemented. Currently blocked by https://github.com/seamapi/phone/issues/165

• #137
• #138

Implement all thermostat endpoints

Sweep: Replace the type assertions with better types

The type assertions using the as keyword should be removed and replaced with stronger types.

Checklist

• Modify src/lib/database/index.ts ✓ 00f8671
• Modify src/lib/middleware/index.ts ! No changes made
• Create src/pages/api/index.tsx ✓ aa465e3
• Modify src/lib/zod/index.ts ! No changes made

Implement climate_setting_schedules/list

`custom_metadata` missing from `Device` schema

`capability_flags` missing from `Device` schema

Introduce Dockerfile for running fake-seam-connect

Introduce Dockerfileand publish docker image to GitHub.

Implement /internal/devicedb/ endpoints

See https://github.com/seamapi/devicedb/tree/main/pages/api/device_models and can import Zod schemas directly from @seamapi/types/devicedb

Device images can be added to /public/devicedb/images in this repo and urls in the API response can be served from https://fake-seam-connect.seam.vc/devicedb/images

• /internal/devicedb/v1/device_models/list
• /internal/devicedb/v1/device_models/get
• /internal/devicedb/v1/manufacturers/list
• /internal/devicedb/v1/manufacturers/get

/internal/phone/user_identities/(load_invitations|get_invitation)

Support JWT auth method

See also seamapi/nextlove#124 and #126

Update Readme to publish a new release

Implement /devices/list_device_providers

Blocking seamapi/react#251

CC @andrii-balitskyi and @seveibar

Emulate fake visionline and assa abloy on fake seam-connect

In order to test the mobile sdk, we need to be able to register an endpoint from fake visionline and simulate reader behaviors. Since we're using fake seam connect, it doesn't hold any references to underlying fakes (double fake problem). In order to get around this we need to implement fake visionline endpoints into fake seam connect. We need everything under the api/_fake endpoints:

• api/_fake/load_credentials
• api/_fake/redeem_invite_code
• api/simulate/readers/list
• api/simulate/readers/unlock

We need it in reference to this section of the sequence diagram:

Add /action_attempts/get

fake-seam-connect `create_invitations` endpoint should never return invitation codes

Delete instead of setting to undefined (blocked by lint rule)

          Can this be deleted from the object instead of set undefined? Maybe not so important if when it is serialized that happens anyway

Originally posted by @razor-x in #81 (comment)

`/workspaces/get` does not return `{ is_sandbox }`

Fake OPTIONS requests

Needed for CORS support.

Implement /access_codes/update

Needed to unblock seamapi/react#312 (comment)