Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

FEAT GUI: Add dataset loading controls and access guidance

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

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

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
領域
api, frontend, testing

調査の方向性

Start with the Datasets section, the shared API/error layer, existing configuration-access checks, and Fluent UI form/status patterns; review the frontend style and component-test instructions. Confirm the prerequisite items and promotion status before starting. Done means mocked and local public/gated flows cover explicit loading, operation states, errors, retry, accessibility, and successful refresh without losing context.

索引モデルが issue の本文から書いたものです。

説明

datasets feature-request GUI not ready yet
Is your feature request related to a problem? Please describe.

Available built-in datasets need a clear loading workflow. Users must understand why a gated dataset cannot load and how to configure access without entering secrets into a new GUI credential store.

Work item 11 of 17 in #2744. Technical prerequisites: items 9-10. Keep not ready yet until promoted.

Describe the solution you'd like

Add explicit Load controls to available-provider cards/detail views and show the provider's supported variant/options before submission.

  • Show source/license information and known credential/gated-access prerequisites. Link to external access instructions or the existing configuration surface where permitted. Do not automatically accept dataset terms.
  • State that loading uses backend credentials and adds data to shared deployment memory. Do not add token fields, display stored tokens, or imply per-user private datasets.
  • Show pending/loading/persisting/success/failure states from the operation API; prevent duplicate submissions and allow safe status recovery while navigating.
  • Explain missing configuration, access denial, offline/upstream errors, invalid options, partial loading, and lost operation status distinctly. Retry must follow the service's semantics.
  • Refresh loaded counts and table availability after success without losing browse filters or return-to-chat context.

Acceptance criteria:

  • Public and gated provider flows work against mocked/local providers without privileged access.
  • A user must explicitly choose Load; viewing a card does not download anything.
  • Configured credentials are never treated as guaranteed gated access.
  • Loading options, duplicate-click protection, errors, retry, and successful refresh are covered by component tests.
  • The UI remains accessible and responsive during a long load and no target is required just to load/browse a dataset.
Describe alternatives you've considered, if relevant

Do not introduce per-user authentication to dataset providers, a password/token manager, background prefetch of all datasets, or unsupported cancellation/resume promises.

Additional context

Build on the Datasets section and shared API/error layer from earlier items. Reuse existing configuration-access checks and Fluent UI form/status patterns. Follow frontend style/test instructions. This completes the built-in provider milestone.

主要言語
Python
スター
4.5k
フォーク
896
平均マージ
3日 2時間
マージ済み PR（30日）
210

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

microsoft/PyRIT のほかの issue

microsoft/PyRIT の issue をすべて見る

似ている issue

Python の issue をもっと見る

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

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