haskell/haskell-ide-engine

Automatic extension detection from package.yaml for Floskell

Open

#1,506 建立於 2019年12月29日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)Haskell (2,358 star) (205 fork)batch import
good first issue

描述

I have several extensions enabled in my package.yaml file in the default-extensions field (e.g. DerivingStrategies), so floskell fails to parse the source file (on seeing deriving stock for example) and reports a syntax error.

Is there any possibility that we automatically detect the default-extensions field in package.yaml file and pass them to floskell? Or perhaps by default enabling some extensions that in general don't break otherwise well-formed programs (e.g. DerivingStrategies, StandaloneDeriving, etc.)?

貢獻者指南

技術棧
無
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Haskell basicsFloskell familiarityYAML parsing
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Examine Floskell's codebase to see how it currently handles language extensions. Look for any existing mechanism to read package.yaml files. If none, consider implementing a parser to extract default extensions and pass them to Floskell. Check the issue comments for any additional context or suggestions from the maintainer.