facebookarchive/atom-ide-ui

Allow setting the diagnostics status bar item to only show counts for the current file

Open

#146 opened on 2018年1月16日

GitHub で見る
 (1 comment) (2 reactions) (0 assignees)JavaScript (937 stars) (110 forks)batch import
enhancementhelp wanted

説明

Description

Allow setting the diagnostics status bar to only show counts for the current file instead of for the entire project. This is available in linter-ui-default as linter-ui-default.statusBarRepresents config.

There is already a checkbox for the diagnostics window itself, this is about the status bar. Instead of a setting, it might be better to make the button in the diagnostics panel effect the status bar too. This will be quite convenient since it will be easily toggleable.

Or maybe the setting could be to select from: "Same as panel", "Project", "File". Where "Same as panel" makes it obey the checkbox in the diagnostics panel and project and file always display project wide or for the current file only regardless of the checkbox.

Versions

  • Atom: 1.23.3
  • Client OS: Windows 10 x64
  • atom-ide-ui: 0.7.1

Additional Details

  • Installed packages (apm ls --installed):
Community Packages (2)
├── atom-ide-ui@0.7.1
└── ide-python@0.5.0

コントリビューターガイド

技術スタック
javascripthtmlcss
領域
frontenddeveloper experience
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Familiarity with Atom package developmentBasic JavaScriptBasic HTMLKnowledge of diagnostics panel
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
45
調査方針
First, examine the diagnostics status bar implementation in the atom ide ui source code, likely in the 'lib' directory. Look for how the current count is calculated (project wide vs file specific). Consider implementing a config similar to linter ui default's 'statusBarRepresents', or tie it to the existing diagnostics panel checkbox. Refer to issue #146 for community discussion. Note that the repository is archived, so contributions may not be merged, but the issue provides a good learning opportunity.