Fix Core and Community plugin list row layout after settings section changes #313

Closed
opened 2026-06-05 20:11:27 +00:00 by steve · 0 comments
Owner

Describe the issue.

Problem

Goal

Scope

Non-goals

Acceptance Criteria

Implementation Notes

Suggested Files or Specs To Inspect

Validation Commands

Follow-up Tasks

Implementation Summary

Removed setting-plugin-list-tab special case; Core and Community plugin lists use Setting.setHeading() with plugin rows in setting-section-body. Added grid-column: 1 / -1 for plugin-extension-setting rows. Validated with api setting-heading tests and workspace check:all.

Describe the issue. ## Problem ## Goal ## Scope ## Non-goals ## Acceptance Criteria ## Implementation Notes ## Suggested Files or Specs To Inspect ## Validation Commands ## Related Issues - Follow-up to #312 — [Align imperative Setting.setHeading with schema section layout](../closed/312-align-imperative-setting-setheading-with-schema-section-layout.md) ## Follow-up Tasks ## Implementation Summary Removed setting-plugin-list-tab special case; Core and Community plugin lists use Setting.setHeading() with plugin rows in setting-section-body. Added grid-column: 1 / -1 for plugin-extension-setting rows. Validated with api setting-heading tests and workspace check:all. <!-- backlog:task_id=TASK-SETTINGS-PLUGIN-LIST-LAYOUT related_issue=312 -->
steve 2026-06-05 20:28:42 +00:00
  • closed this issue
  • added
    done
    and removed
    open
    labels
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lapis-notes/lapis#313
No description provided.