ipfs/ipfs-companion

Import to Files on My Node does not work on disabled origins

Open

#1,000 创建于 2021年5月10日

在 GitHub 查看
 (0 评论) (0 反应) (1 负责人)JavaScript (1,992 star) (364 fork)batch import
P1help wantedkind/bug

描述

v2.19.0 introduced "Import to Files on My Node" feature in the main browser action menu:

2021-05-10--13-53-29

User can disable IPFS integrations on specific origin, and when that happens, this feature does nothing.

We need to either:

  • wire things up so the proper /ipns/{dnslink-name} content path is used, even when page is at https://{dnslink-name}
  • OR fade out this option so it is obvious it is deactivated

贡献者指南

技术栈
javascript
领域
frontend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaScriptbrowser extension fundamentalsIPFS
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
Examine the browser action popup code (likely under src/popup) to understand how the 'Import to Files on My Node' button is implemented. Investigate how disabled origins are tracked and where the content path resolution occurs. The two proposed solutions involve either modifying the popup to use the proper /ipns/{dnslink name} content path or graying out the option when the origin is disabled. Check if the assignee has left any comments or linked PRs for additional context.