Skip to content

issues Search Results · language:B4X language:C++ language:JavaScript language:HTML language:TypeScript language:Python

Filter by

70.3M results  (828 ms)

70.3M results

Problem Each provider shim declares its own version as a Go const literal in config.go. The constant has to be hand-edited every release. Today, all four shim version strings are stale relative to the ...

Describe the bug A language inconsistency has been identified in the Enatega Multivendor Admin Dashboard. After changing the language, the status in the Dispatch and Withdraw Requests sections is still ...

owner: service:coaching depends_on: [] blocks: [] spec_sections: [] blueprint_sections: [ §XIII ] maturity_target: organized acceptance: - coaching.briefings DDL with domain_id, focus_area_id, content_md, ...
frontend
service:coaching
spec
spec-gap

mans not even using exception handling

Sammanfattning Vid CSV-import av kontrakt lagrar importLeases bara depositAmount som ett tal på Lease-raden — det skapas ingen Deposit-post och ingen bokföring. En ägare som migrerar deponerade hyror ...
bokforings-flagged
bug
priority:high

Large PR Detected\n\n- PR: #449\n- Changed Lines: 1191\n- Threshold: 500\n\nThis PR exceeds the recommended maximum of 500 changed lines. Consider splitting it into smaller, focused PRs for easier review.\n\n ...

Several deployment and security risks were identified in the WPAI SaaS deployment process and guide: Critical Risks 1. Hardcoded Secret Exposure: No clear warning to keep sensitive files like .env.local ...
bug

Gap opened by the #93 fix The #93 fix makes validateSpec skip in-file phase-section checks for split-layout specs (type: requirements|design|tasks) — correct (a design file has no ## Plan by design; Model ...
feat
inbox

owner: service:vault depends_on: [] blocks: [] spec_sections: [ §3.5 ] blueprint_sections: [ §17 , §XI ] maturity_target: lender_ready acceptance: - Readiness Packaging Engine assembles lender package ...
service:marketplace
service:vault
spec
spec-gap

目的 父の樹会ホームページのリニューアルに向けて、サイト全体のデザイン方針を作成する。 Issue #2 で整理した「対象者・公開範囲」、Issue #3 で整理した「サイトマップ案」、Issue #4 で整理した「トップページ構成案」をもとに、HTMLプロトタイプ作成前のデザイン方針を明確にする。 背景 現行サイトは情報が古く、デザイン面でも古さやチープさが目立ってきている。 リニューアル後は、見た目を新しくするだけでなく、利用者にとって読みやすく、安心感があり、更新しやすいサイトにする必要がある。 ...
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.