sub-store-org / sub-store-org/Sub-Store

分享链接/订阅链接优化

Open
#459 28 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10.5k
Forks
1.4k
Avg merge
5h 31m
Merged PRs (30d)
10

Description

  1. 复制链接不包含主域名,仅有路径,需手动拼接
    无论是订阅链接还是文件链接,无论时临时访问还是分享链接,复制出来的地址只包含路径部分,不携带主域名,导致用户必须手动添加域名才能正确访问,使用体验不佳,建议复制时自动包含完整 URL。

  2. 分享链接不同订阅对象却提示 token 已存在
    分享链接格式示例:/share/sub/justmysocks?token=123456
    当前逻辑中,token 的唯一性判断似乎未绑定订阅对象名称,导致不同订阅对象使用相同 token 时出现“token 已存在”的错误提示。
    建议:

  • 若 token 仅在订阅对象范围内唯一,则应结合订阅对象名进行唯一性校验;
  • 若 token 保证全局唯一,则分享链接中可以省略订阅对象名,简化 URL。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the /share/sub/justmysocks?token=123456 flow and the subscription and file-link copy paths mentioned in the issue. Confirm whether copied links should include the main domain and determine whether token uniqueness is scoped to the subscription object or global. Done means both link types produce usable URLs and valid tokens no longer conflict incorrectly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.