[CHORE]: Prepare for CARTO basemap API key enforcement
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
调研方向
Start by reading the layout.map.style documentation and the tests and baselines that use CARTO styles. Confirm the vector key enforcement timeline with CARTO or the maintainers, then decide how Plotly should handle it and document that outcome for users. Done means the docs explain CARTO's terms and key requirements, and tests and baselines no longer depend on live CARTO data.
由索引模型根据 Issue 内容生成。
描述
Description
Prepare plotly.js for CARTO enforcing its basemap API key on vector tiles. Find out when enforcement starts, decide how Plotly handles it, and document the outcome for users. Today CARTO enforces the key only for raster tiles, which Plotly does not use.
Why should this change be made?
CARTO's docs say an API key is required for all CARTO basemaps. Plotly's carto-* styles and the legacy basic, streets, outdoors, light and dark styles load keyless vector styles from basemaps.cartocdn.com/gl/. If CARTO enforces the key for vector tiles, all of these styles stop loading for every user. Plotly has no way to pass a key. A shared key in the bundle would count against one quota and break CARTO's terms.
Scope
- Ask CARTO or the maintainers when vector enforcement starts
- Decide what Plotly does when it starts: document the
?key=workaround throughmap.style, or choose a default basemap that needs no key - Add a note under
layout.map.stylethat CARTO styles fall under CARTO's terms and may need an API key - Stop the tests and baselines from using the live CARTO style, so they do not break when CARTO changes its data or its key rules (see the baseline breakage after CARTO's 2026-10-21 move to
carto.streets/v2)
Notes
- CARTO docs: https://github.com/CartoDB/basemap-styles#readme
- Free tiers: 5M tile requests a month for non-commercial use, 1M for commercial use
- Terms: https://carto.com/legal/basemap-terms/
- Observed on 2026-10-22: a keyless raster tile returns an "API KEY REQUIRED" watermark. Keyless vector style, tile and font requests return 200 with real data, and so do requests with a made-up key.
- 主要语言
- JavaScript
- 星标
- 18.4k
- 派生
- 2.1k
- 平均合并
- 2 天 16 小时
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
plotly/plotly.js 的其他 Issue
-
[BUG]: `events` is required but not declared in dependencies可能已有人在做 @KoolADE85 于 6 天前认领。 未关闭bug P3 size: 1
难度 2/5 1-3 小时 新手友好度 83/100
plotly/plotly.js#8163 · 已指派 1 人 ·
维护者通常 1 天内回复
-
[BUG]: `sankey`: `node.x` / `node.y` of `0` is ignored可能已有人在做 @adimalkar 于 11 天前认领。 未关闭bug P3 size: 1
难度 2/5 1-3 小时 新手友好度 75/100
plotly/plotly.js#8150 · 1 条评论 ·
维护者通常 1 天内回复
-
[BUG]: `scatterpolargl` drops points between 10000 and 100000 points可能已有人在做 @Tanishdete333 于 11 天前认领。 未关闭bug P3 size: 1
难度 2/5 1-3 小时 新手友好度 82/100
plotly/plotly.js#8148 · 1 条评论 ·
维护者通常 1 天内回复
-
[BUG]: findEmpties throws "iterated with no new neighbors" for large NaN regions in contour (double-precision underflow)可能已有人在做 @davrens101 于 10 天前认领。 未关闭bug P3 size: 3
难度 2/5 1-3 小时 新手友好度 86/100
plotly/plotly.js#8108 · 4 条评论 ·
维护者通常 1 天内回复
-
chore P3 plotly-internal size: 3 task
难度 2/5 1-3 小时 新手友好度 77/100
plotly/plotly.js#8064 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
channels:add check:passed
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
-
难度 2/5 1-3 小时 新手友好度 66/100
SasanLabs/VulnerableApp#912 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
[chore]: Force minimatch 11.0.1 in the CI scripts' jest tooling (Dependabot #140)可能已有人在做 @alishair7071 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
jaegertracing/jaeger#10133 · 2 条评论 ·
维护者通常 1 天内回复