feat: Trafero v0.2.0 - Tdarr v2 native Android client with slow-connection resilience
Full client for the Tdarr /api/v2 JSON API (jobs, library, nodes, stats, logs, settings, flows, multi-server switcher) plus v0.2.0 resilience: per-server timeout + slow-connection mode, retry-with-backoff on read polls, last-good-data + reconnecting chip, 60s poll backoff after repeated failures, and keep-alive eviction on app resume. Includes GPL-3.0 licensing (LICENSE/NOTICE), README, CONTRIBUTING, PREVIOUS_HISTORY, issue/PR templates, CI release-notes script, keystore docs and the vendored OpenAPI 2.0 spec.
This commit is contained in:
commit
312858e8f6
50 files changed
+4446
No files matched your search
@@ -0,0 +1,61 @@
|
||||
name: Feature Request
|
||||
description: Suggest a new feature for Trafero.
|
||||
labels:
|
||||
- kind/feature
|
||||
body:
|
||||
- type: input
|
||||
id: summary
|
||||
attributes:
|
||||
label: Summary
|
||||
description: One-line description of the feature.
|
||||
placeholder: e.g. "Add a push alert when the error stack grows"
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: problem
|
||||
attributes:
|
||||
label: Problem / motivation
|
||||
description: What problem does this solve? What can the user do today that they can't, or what do they do today that's harder than it should be?
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: proposal
|
||||
attributes:
|
||||
label: Proposed solution
|
||||
description: Describe how you imagine the feature working. Screenshots, mockups, or links welcome.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: alternatives
|
||||
attributes:
|
||||
label: Alternatives considered
|
||||
description: What other approaches did you consider, and why is your proposal better?
|
||||
validations:
|
||||
required: false
|
||||
- type: textarea
|
||||
id: roadmap
|
||||
attributes:
|
||||
label: Roadmap relevance
|
||||
description: |
|
||||
Has someone asked for this before - link or mention any related issues.
|
||||
If not, do you think it should be added there before implementing?
|
||||
validations:
|
||||
required: false
|
||||
- type: dropdown
|
||||
id: privacy
|
||||
attributes:
|
||||
label: Privacy impact
|
||||
description: Does this feature touch anything that leaves the device, scans user data, or requires a new permission?
|
||||
options:
|
||||
- None — fully on-device
|
||||
- Adds new on-device processing only
|
||||
- Requires a new optional permission
|
||||
- Requires network access (almost certainly out of scope for now)
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: extra
|
||||
attributes:
|
||||
label: Anything else?
|
||||
validations:
|
||||
required: false
|
||||
Reference in new issue
Block a user