mk3008 / mk3008/rawsql-ts

rawsql-ts 用の dogfooding configuration / adapter を用意する

Open
#580 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
30
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Summary

Finding Compiler を rawsql-ts で dogfooding する際、repo 内の issue / PR / review だけでなく、npm consumer / packed tarball consumer まで対象に含める adapter / configuration を用意する。

repo 内 dogfooding だけでは consumer failure を十分に拾えない。
そのため、customer-consumer failure を正式な finding source として扱う。

Scope

  • package placement の決定
  • rawsql-ts repo での storage path 決定
  • issue / PR / review / CI failure / publish failure / customer failure から finding を起こすルール
  • npm consumer failure のサンプル finding 化
  • initial dogfooding scenario 作成
  • customer guard への昇格サンプル作成

Required Scenarios

  • repo 内 failure
  • GitHub Actions failure
  • publish failure
  • npm consumer smoke failure
  • scaffold compatibility failure

Done Criteria

  • rawsql-ts で 3 件以上の実 finding を扱える
  • うち 1 件以上が customer failure である
  • finding から guard / verification / customer test までの流れを試せる
  • core が rawsql-ts 固有実装に汚染されていない

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by deciding the package placement and rawsql-ts storage path, then map the required finding sources and dogfooding scenarios. Use the repo-internal, GitHub Actions, publish, npm consumer, and scaffold compatibility failures as the initial verification plan. Done means handling at least three real findings, including one customer failure, and exercising the path from finding to guard, verification, and customer test without polluting core code.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.