|
| 1 | +name: Parity gap (vs JSS) |
| 2 | +description: Report behaviour that differs from the reference Solid server implementation |
| 3 | +title: "[parity] " |
| 4 | +labels: ["parity", "triage"] |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + Use this template when solid-pod-rs disagrees with a reference |
| 10 | + implementation (typically JavaScriptSolidServer, JSS) on a |
| 11 | + specification-level behaviour. See `PARITY-CHECKLIST.md` for the running |
| 12 | + list of tracked items. |
| 13 | +
|
| 14 | + - type: input |
| 15 | + id: spec |
| 16 | + attributes: |
| 17 | + label: Specification section |
| 18 | + description: Which spec + section? (e.g. Solid Protocol §5.1, LDP §4.2) |
| 19 | + placeholder: "Solid Protocol v0.10.0 §5.2 — WAC inheritance" |
| 20 | + validations: |
| 21 | + required: true |
| 22 | + |
| 23 | + - type: input |
| 24 | + id: reference |
| 25 | + attributes: |
| 26 | + label: Reference implementation |
| 27 | + description: Which implementation + version was the behaviour compared against? |
| 28 | + placeholder: "javascript-solid-server 0.0.86" |
| 29 | + validations: |
| 30 | + required: true |
| 31 | + |
| 32 | + - type: textarea |
| 33 | + id: scenario |
| 34 | + attributes: |
| 35 | + label: Scenario |
| 36 | + description: The exact request(s) or operation(s) used to demonstrate the divergence. |
| 37 | + render: http |
| 38 | + validations: |
| 39 | + required: true |
| 40 | + |
| 41 | + - type: textarea |
| 42 | + id: jss-behaviour |
| 43 | + attributes: |
| 44 | + label: JSS / reference behaviour |
| 45 | + description: Response body, status codes, headers — include all observable effects. |
| 46 | + render: shell |
| 47 | + validations: |
| 48 | + required: true |
| 49 | + |
| 50 | + - type: textarea |
| 51 | + id: solid-pod-rs-behaviour |
| 52 | + attributes: |
| 53 | + label: solid-pod-rs behaviour |
| 54 | + description: What solid-pod-rs actually does. Same level of detail as above. |
| 55 | + render: shell |
| 56 | + validations: |
| 57 | + required: true |
| 58 | + |
| 59 | + - type: dropdown |
| 60 | + id: severity |
| 61 | + attributes: |
| 62 | + label: Severity |
| 63 | + options: |
| 64 | + - Blocks interop with existing clients |
| 65 | + - Spec non-conformance, workaround exists |
| 66 | + - Edge case / clarification needed |
| 67 | + validations: |
| 68 | + required: true |
| 69 | + |
| 70 | + - type: textarea |
| 71 | + id: test-case |
| 72 | + attributes: |
| 73 | + label: Suggested regression test |
| 74 | + description: If you have a pytest/cargo-test snippet or curl transcript, paste it here. |
| 75 | + render: rust |
| 76 | + |
| 77 | + - type: checkboxes |
| 78 | + id: parity-checklist |
| 79 | + attributes: |
| 80 | + label: Parity checklist |
| 81 | + options: |
| 82 | + - label: I have searched `PARITY-CHECKLIST.md` and this gap is not already tracked |
| 83 | + - label: I have confirmed the behaviour on the latest `main` |
| 84 | + - label: I am willing to contribute a regression test |
0 commit comments