@pidrang/primeng: PrimeNG UI adapter

オープン
  • 何か問題がありますか？
#7 コメント 1 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@fetrarij がすでに取り組んでいます。

2026年9月25日 から。

評価

この issue はまだ評価されていません。

説明

enhancement layer: library pkg: new

Context

Existing #7 requests a PrimeNG adapter/demo matching Material. README.md:11 mentions PrimeNG but there is no libs/primeng implementation; libs/material/src/lib/resource-table/resource-table.ts:18 and resource-form/resource-form.ts:36 define the reference APIs. The supplied project context reports a PrimeNG 22 redistribution/OEM-license blocker; this is not a legal conclusion verified by the code audit.

Scope

  • Keep the issue blocked until fetrarij obtains authoritative licensing/redistribution clarification and records a proceed/defer/close decision with the relevant source.
  • If approved, implement the existing intended PrimeNG ResourceTable/ResourceForm adapter and demo against the current core contracts, using only core among Pidrang runtime dependencies.
  • Add the same actions/paging/forms/auth consumer checks, package metadata and production demo integration used for the other adapters.

Out of scope

Purchasing a license without owner approval, claiming legal clearance from this audit, opening a duplicate adapter or silently substituting another UI library.

Acceptance criteria

  • Owner decision and authoritative licensing basis are recorded before distribution work begins.
  • If proceeding, adapter API parity, clean install/build and Playwright CRUD/auth checks pass.
  • If deferred/closed, roadmap honestly reflects the decision and does not advertise a shipped adapter.

Notes for the dev

Keep assignee fetrarij. Depends on licensing clearance and released core contracts; coordinate later hosting with #37/pidrang/pidrang.github.io#2. Do not block 0.1.0 on this optional adapter.

Rules: no code comments, no any/$any; standalone components, signals and inject(). Core production imports only @angular/core and local core modules, never router/common/forms/UI. Other Pidrang libraries depend only on core, except @pidrang/cli-supabase which depends on @pidrang/cli as per the package graph in CLAUDE.md; apps compose adapters. Use conventional commits. For UI changes, validate with Playwright against pnpm exec nx serve demo-material and pnpm exec nx serve demo-tailwind; record tested paths and failures. Also validate generated UI in an external consumer fixture when affected.

Original description

ROADMAP.md Phase 7, later without core changes. Same shape as @pidrang/material but for PrimeNG components, consuming core's reactive primitives (injectResourceList, injectDataProvider, injectAuthSession) directly. Depends on @pidrang/core only.

Wire it into a new apps/demo-primeng app (same three resources as the existing demo — users/products/orders), so it's actually visible/comparable, not just a library nobody renders. Same pattern #30 used for @pidrang/material + apps/demo.

主要言語
TypeScript
スター
2
フォーク
2
平均マージ
9時間 17分
マージ済み PR（30日）
48

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pidrang/pidrang のほかの issue

pidrang/pidrang の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。