Skip to content

feat(FR-2618): add sToken login boundary component spec#6828

Merged
graphite-app[bot] merged 1 commit into
mainfrom
04-21-feat_add_stoken_login_boundary_component_spec_draft_
Apr 23, 2026
Merged

feat(FR-2618): add sToken login boundary component spec#6828
graphite-app[bot] merged 1 commit into
mainfrom
04-21-feat_add_stoken_login_boundary_component_spec_draft_

Conversation

@nowgnuesLee

@nowgnuesLee nowgnuesLee commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

Resolves FR-2618 (sub-issue of Epic FR-2616)

Summary

  • Add feature spec for a reusable STokenLoginBoundary React component that extracts the duplicated sToken login logic from LoginView.tsx and EduAppLauncher.tsx into a single, Error-Boundary-style component.
  • Stories planned under Epic FR-2616: 3 (new component + endpoint-hook generalization; LoginView migration; EduAppLauncher migration).

Jira

Scope of this PR

  • Spec documents only. No production code (LoginView, EduAppLauncher) is touched.
  • Files added:
    • .specs/draft-stoken-login-boundary/spec.md (Korean)
    • .specs/draft-stoken-login-boundary/metadata.json

Follow-up

  • Rename directory from draft-stoken-login-boundary to FR-2616-stoken-login-boundary (after this PR merges).
  • Run /fw:dev-plan FR-2616 to break the spec into the three planned stories.

Test plan

  • Spec file renders correctly on GitHub (Korean content).
  • Acceptance criteria are testable and map 1:1 to the three planned stories.
  • Open Questions are explicitly marked for resolution in dev-plan.

@github-actions github-actions Bot added the size:L 100~500 LoC label Apr 21, 2026

nowgnuesLee commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • flow:merge-queue - adds this PR to the back of the merge queue
  • flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@nowgnuesLee nowgnuesLee changed the title feat: add sToken login boundary component spec (draft) feat(FR-2618): add sToken login boundary component spec Apr 21, 2026
@nowgnuesLee nowgnuesLee marked this pull request as ready for review April 21, 2026 09:00
Copilot AI review requested due to automatic review settings April 21, 2026 09:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a draft specification (Korean) for extracting the duplicated sToken-based SSO login flow into a reusable STokenLoginBoundary React component, plus accompanying spec metadata for FR-2616/FR-2618.

Changes:

  • Add a detailed component design spec covering API, error taxonomy, auth sequence, migration plan, and test strategy.
  • Add metadata JSON describing the epic/spec task and proposed implementation stories.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.specs/draft-stoken-login-boundary/spec.md Draft spec defining STokenLoginBoundary behavior, API, error handling, migration stories, and acceptance criteria.
.specs/draft-stoken-login-boundary/metadata.json Metadata for tracking FR-2616/FR-2618 and proposed stories derived from the spec.

Comment thread .specs/draft-stoken-login-boundary/spec.md Outdated
Comment thread .specs/draft-stoken-login-boundary/spec.md Outdated
@nowgnuesLee nowgnuesLee requested a review from yomybaby April 21, 2026 13:18
@github-actions github-actions Bot added size:XL 500~ LoC and removed size:L 100~500 LoC labels Apr 21, 2026
@nowgnuesLee nowgnuesLee force-pushed the 04-21-feat_add_stoken_login_boundary_component_spec_draft_ branch from 27e04f0 to 9e62aef Compare April 22, 2026 03:53
@nowgnuesLee nowgnuesLee force-pushed the 04-21-feat_add_stoken_login_boundary_component_spec_draft_ branch from 9e62aef to bff5d15 Compare April 23, 2026 07:57

@yomybaby yomybaby left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@graphite-app

graphite-app Bot commented Apr 23, 2026

Copy link
Copy Markdown

Merge activity

Resolves FR-2618 (sub-issue of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

## Summary

- Add feature spec for a reusable `STokenLoginBoundary` React component that extracts the duplicated sToken login logic from `LoginView.tsx` and `EduAppLauncher.tsx` into a single, Error-Boundary-style component.
- Stories planned under Epic FR-2616: 3 (new component + endpoint-hook generalization; LoginView migration; EduAppLauncher migration).

## Jira

- Epic: [FR-2616 — Extract sToken login flow into reusable boundary component](https://lablup.atlassian.net/browse/FR-2616)
- Spec Task (this PR): [FR-2618 — Define sToken login boundary component spec](https://lablup.atlassian.net/browse/FR-2618)

## Scope of this PR

- Spec documents only. No production code (LoginView, EduAppLauncher) is touched.
- Files added:
  - `.specs/draft-stoken-login-boundary/spec.md` (Korean)
  - `.specs/draft-stoken-login-boundary/metadata.json`

## Follow-up

- [ ] Rename directory from `draft-stoken-login-boundary` to `FR-2616-stoken-login-boundary` (after this PR merges).
- [ ] Run `/fw:dev-plan FR-2616` to break the spec into the three planned stories.

## Test plan

- [ ] Spec file renders correctly on GitHub (Korean content).
- [ ] Acceptance criteria are testable and map 1:1 to the three planned stories.
- [ ] Open Questions are explicitly marked for resolution in dev-plan.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
@graphite-app graphite-app Bot force-pushed the 04-21-feat_add_stoken_login_boundary_component_spec_draft_ branch from bff5d15 to ce58ca6 Compare April 23, 2026 10:32
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
…int (#6850)

Resolves FR-2628 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
)

Resolves FR-2629 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
…rning (#6852)

Resolves FR-2630 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
Resolves FR-2631 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
…Boundary (#6855)

Resolves FR-2632 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
graphite-app Bot pushed a commit that referenced this pull request Apr 23, 2026
Resolves FR-2633 (sub-task of Epic [FR-2616](https://lablup.atlassian.net/browse/FR-2616))

resolves #NNN (FR-MMM)
<!-- replace NNN, MMM with the GitHub issue number and the corresponding Jira issue number. -->

<!--
Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes,
and how it affects the users and other developers.
-->

**Checklist:** (if applicable)

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

## Stack

This PR is part of the Story 1 stack for Epic FR-2616 (Extract sToken login flow into reusable boundary component). See the [dev plan](../blob/main/.specs/draft-stoken-login-boundary/dev-plan.md) for the full scope. The Story 1 PR stack is #6850#6851#6852#6853#6854#6855#6856 on top of spec PR #6828.

[FR-2616]: https://lablup.atlassian.net/browse/FR-2616?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
@graphite-app graphite-app Bot merged commit ce58ca6 into main Apr 23, 2026
8 checks passed
@graphite-app graphite-app Bot deleted the 04-21-feat_add_stoken_login_boundary_component_spec_draft_ branch April 23, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XL 500~ LoC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants