vim-jp / vim-jp/reading-vimrc

更新スクリプトが少し不便

Open
#10 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
107
Forks
10
PR merge metrics
No merged PRs in 30d

Description

#6 から移行

Pythonで書きましたが、標準ライブラリにyamlなかったので面倒くさくて、現状_data/archives.ymlに問答無用で追記するなどといった残念仕様です。

ちゃんとidみてかぶってたら上書きor無視みたいな感じに出来たほうがよさげ。

Rubyだとyaml扱えるライブラリ標準であるらしいので、Rubyのほうが書きやすいかも

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #6 and locating the update script that writes to _data/archives.yml. Inspect how archive IDs are currently handled, then define and verify the intended behavior when an ID already exists—overwriting it or ignoring the update—without creating duplicate entries.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, ruby
Domain
content, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.