Rooted, unrooted path semantics

未关闭
#3,203 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
haskell
领域
backend

调研方向

Read the internal unreleased typed modules and locate splitRoot and eqPath, the two places named in the issue. Compare their current handling of leading-dot paths with the proposed default convention and the option to disable the distinction. Done means the default follows common rooted and unrooted path conventions, with an option available if needed.

由索引模型根据 Issue 内容生成。

描述

api:breaking aspect:api aspect:filesystem

Treating paths with a leading dot to be anchored and the ones not starting with a leading dot as unanchored path segments may fight the common intuition that those paths are the same. This abstraction may not be worth changing that convention as it is too common and well ingrained. The only places where this distinction is made is splitRoot and eqPath, the latter has an option to disable it. But we can keep the default aligned with common conventions and maybe have an option to treat it differently if needed. The internal unreleased, typed modules can be changed accordingly.

主要语言
Haskell
星标
926
派生
71
平均合并
6 小时 49 分钟
30 天内合并 PR
3

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

composewell/streamly 的其他 Issue

查看 composewell/streamly 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。