bot-hermes
8f5cfdcd62
- server: write routes for all three providers (issue/PR comments, inline review-comment replies, issue/MR updates w/ labels-assignees-milestone, review submit, draft toggle) - ui: ForgeProvider gains six write ops; shared action components (composer, thread reply, state/review/draft/metadata/edit) wired into ForgeEntityDetailView and GitHub PR Overview
19 lines
936 B
TypeScript
19 lines
936 B
TypeScript
/**
|
|
* Write-action UI for forge issues and pull requests.
|
|
*
|
|
* Every component is capability- and method-gated: it renders nothing (or a
|
|
* sub-affordance) unless the provider implements the underlying write method
|
|
* and its capability flag is set. Components call the facade directly, toast
|
|
* stable i18n messages on failure (never raw error text), and report success
|
|
* through `onChanged`/`onPosted` callbacks so the owning view can refetch or
|
|
* update local state.
|
|
*/
|
|
export { ForgeCommentComposer } from './ForgeCommentComposer';
|
|
export { ForgeThreadReply } from './ForgeThreadReply';
|
|
export { ForgeStateActions } from './ForgeStateActions';
|
|
export { ForgeReviewActions } from './ForgeReviewActions';
|
|
export { ForgeDraftToggle } from './ForgeDraftToggle';
|
|
export { ForgeMetadataEditor } from './ForgeMetadataEditor';
|
|
export { ForgeEditForm } from './ForgeEditForm';
|
|
export { ForgeEntityActions } from './ForgeEntityActions';
|