seamapi/fake-template

Template for creating Fake Devices

fake-template's Issues

Tweak stale bot config

          we don't currently have stale issues set up on most fakes, I think in general because fake issues are more around tech debt or non-critical missing features and are usually lower priority

don't have a super strong opinion, I do think a stale PR config is good everywhere 👍

Originally posted by @codetheweb in #12 (comment)

disable exactOptionalPropertyTypes

This rule makes code more complex for little gain (doesn't prevent a very common bug)

Should use `nextlove` and have scripts for generating `public/openapi.json` and route-types.ts

Refactor `MethodsOnly` to `ConditionalPick`

    🐧 same as `ConditionalPick` from type fest

Originally posted by @codetheweb in #7 (comment)

Accept passed port option for `startServer()`

Migrate database to Zustand

https://github.com/seamapi/seam-connect/issues/581

Remove alpha/beta pattern. Prefer specially tagged publish for any PR

The alpha/beta pattern encourages large reviews and doesn't match the "small pr, fast ship" culture

Alpha/beta also doesn't work from a git history perspective. Alpha/beta must necessarily be forced pushed to as things are squashed to main

Instead, every PR created against a fake should publish something as a specially tagged version.

• Remove alpha/beta pattern
• Introduce tagged versions for PR branches

Path to Open Source

• Make sure no customer data or leaked internal info is in repo
• Template assumes private repo/package setup (should this be changed)