spaps-issue-reporting-react 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -66,11 +66,15 @@ export function AppShell() {
|
|
|
66
66
|
## What Your App Still Owns
|
|
67
67
|
|
|
68
68
|
- A client with `issueReporting.getStatus`, `list`, `get`, `create`, `update`, and `reply`.
|
|
69
|
+
- Any auth and token refresh behavior needed by that client.
|
|
69
70
|
- Eligibility rules such as feature flags, account state, or role checks.
|
|
70
71
|
- The current principal ID and optional role hint passed into the provider.
|
|
71
72
|
- Whether users can switch between `mine` and `tenant` queue scope.
|
|
72
73
|
- Styling integration if your build strips package utility classes.
|
|
73
74
|
- Any app-specific copy overrides.
|
|
75
|
+
- Origin registration on the owning SPAPS application if the browser calls SPAPS directly with a publishable key.
|
|
76
|
+
|
|
77
|
+
For direct browser integrations, `allowed_origins` is stored on the SPAPS `applications` row that owns the publishable key. It is not configured on this package. If multiple hostnames share one SPAPS application, put all of them on that row. Updating `allowed_origins` does not require restarting SPAPS.
|
|
74
78
|
|
|
75
79
|
## Exported Surface
|
|
76
80
|
|
|
@@ -147,6 +151,10 @@ Yes. Drive that from `isEligible`.
|
|
|
147
151
|
|
|
148
152
|
No. It only renders scope choices that your app explicitly allows.
|
|
149
153
|
|
|
154
|
+
### Does this package manage CORS or `allowed_origins`?
|
|
155
|
+
|
|
156
|
+
No. This package is UI only. If your browser app calls SPAPS directly with a publishable key, the relevant SPAPS application row must include that browser origin in `allowed_origins`.
|
|
157
|
+
|
|
150
158
|
## About Contributions
|
|
151
159
|
|
|
152
160
|
> *About Contributions:* Please don't take this the wrong way, but I do not accept outside contributions for any of my projects. I simply don't have the mental bandwidth to review anything, and it's my name on the thing, so I'm responsible for any problems it causes; thus, the risk-reward is highly asymmetric from my perspective. I'd also have to worry about other "stakeholders," which seems unwise for tools I mostly make for myself for free. Feel free to submit issues, and even PRs if you want to illustrate a proposed fix, but know I won't merge them directly. Instead, I'll have Claude or Codex review submissions via `gh` and independently decide whether and how to address them. Bug reports in particular are welcome. Sorry if this offends, but I want to avoid wasted time and hurt feelings. I understand this isn't in sync with the prevailing open-source ethos that seeks community contributions, but it's the only way I can move at this velocity and keep my sanity.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spaps-issue-reporting-react",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Shared React issue-reporting UI for Sweet Potato platform consumers",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -38,7 +38,7 @@
|
|
|
38
38
|
"@radix-ui/react-dialog": "^1.1.15",
|
|
39
39
|
"@radix-ui/react-popover": "^1.1.15",
|
|
40
40
|
"date-fns": "^4.1.0",
|
|
41
|
-
"spaps-types": "^1.1.
|
|
41
|
+
"spaps-types": "^1.1.2"
|
|
42
42
|
},
|
|
43
43
|
"peerDependencies": {
|
|
44
44
|
"@tanstack/react-query": ">=5.0.0",
|