Suggestion: Selecting modules that required import
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- vim
- Domain
- tooling
Research direction
Start with this issue's checklist and the linked tsuyoshicho/vital-codec project to compare the proposed Crypt, Data, Hash, ID, and Random modules with what vital.vim already provides. Done would require an agreed, bounded selection of modules and clear acceptance criteria; no repository files or tests are named here.
Written by the indexing model from the issue text.
Description
自前開発している tsuyoshicho/vital-codec: vital module for Encode/Decode logics から、持ち込みがあったら嬉しい、というものはあるか、確認していただけると嬉しいです。
- vital
- Crypt
- MAC
- HMAC (パッケージ名と微変更あり) : RFC 2104 - HMAC: Keyed-Hashing for Message Authentication (最新はRFC 6151らしい..)
- Password
- MAC
- Data
- Base16 : RFC 4648 Base16 Data.List.Byteを使う
- Base32x (Base32/RFC4648のラッパーに変更、vital.vimへ導入時はBase32に戻す)
- Base32
- Base32 : (Base32 系 共通処理)
- RFC4648 (元Data.Base32) : RFC 4648 Base32 Standard
- Crockford : Crockford 's Base32
- Hex : RFC 4648 Base32 Hex variant
- Base64x (Base64/RFC4648のラッパーに変更、vital.vimへ導入時はBase64に戻す)
- Base64
- Base64 : (Base64 系 共通処理)
- RFC4648 (元Data.Base64) : RFC 4648 Base64 Standard
- URLSafe : RFC 4648 Base64 URL Safe variant
- List
- Byte : NumberなListとblob/string/hexstring/intの相互変換
- Hash
- MD5x (微変更あり、vital.vimへ導入時はMD5に戻す) : ハッシュ名やサイズを持たせている
- SHA1x (微変更あり、vital.vimへ導入時はSHA1に戻す) : ハッシュ名やサイズを持たせている
- ID
- GUID : Microsoft GUID for UUID variant
- ULID : ulid/spec: The canonical spec for ulid
- UUID : RFC 4122 - A Universally Unique IDentifier (UUID) URN Namespace
- UUID :
- Namespace : UUIDが定義しているNamespace値
- Random
- System (明かなジョークなので、たぶんなし) : /dev/randomとかなるべくOS提供で動く乱数
- Extra
- FixedData : テスト用の固定値を使うための乱数実装
- Vim
- Type
- Number : uintXやrotate処理 (たぶん一部はbitwiseへ移動させたほうがよいと思っている)
- Blob : uintxでの生成とand/or/invert/xor addあり
- Type
- Crypt
- Dominant language
- Vim Script
- Stars
- 586
- Forks
- 64
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vim-jp/vital.vim
-
Web.HTTP の非同期実行を行いたいPossibly taken @mikoto2000 claimed this 300 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Fix and feature: Add python setup in Github workflowMay be free again @tsuyoshicho claimed this 896 days ago, and no pull request is open. Open
-
Vim9.x: support change Vim 8.2/9.0 to Vim 9.0/9.1May be free again @tsuyoshicho claimed this 947 days ago, and no pull request is open. Open
-
feat: Bitwise.vim: bitwise shift operatorMay be free again @tsuyoshicho claimed this 1571 days ago, and no pull request is open. Open
-
Data.List: Deprecate function in string formMay be free again @ujihisa claimed this 2130 days ago, and no pull request is open. Open
All issues in vim-jp/vital.vim
Similar issues
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#673 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
sleeyax/promptfiles#20 ·
-
feature-request mini.icons
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
IBRAHIMDANS/i18nSupportPlus#577 · 3 comments ·
Maintainers usually reply within 1 day
-
docs: the dev-setup table and AGENTS.md name the reviewed_by guard that CI's Changelog job runsOpenarea: tools documentation good first issue ready for a contributor
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eyalgolan/statecraft-israel#873 · 1 comment ·
Maintainers usually reply within 1 day