keystonejs/keystone-classic

add an option to ignore/filter files in the importer

Open

#3,690 opened on 2016年11月12日

GitHub で見る
 (5 comments) (0 reactions) (0 assignees)JavaScript (14,656 stars) (2,288 forks)batch import
enhancementhelp wantedneeds input

説明

I'm currently trying to enhance a project, which is based on the MERN stack, with a keystone backend – something i successfully did with MERN 1.0 and Keystone 3.x. Now i ran into an issue while i tried to import my models via .import('models') caused by the importer who recursively went through the models folder and tried to add the test files as well.

models/
├── __tests__
│   └── post.spec.js
└── post.js

I now that this is a very specific use case but it could be handy to have some kind of filter mechianism in the importer if you're adding the keystone backend to an existing express based app.

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

技術スタック
javascriptnodejs
領域
backendtooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Node.js basicsFamiliarity with Keystone importer
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
75
調査方針
The importer recursively loads files from a directory; this issue requests an option to exclude certain files (e.g., test files). Look at the existing import mechanism in the Keystone classic codebase, likely in `lib/importer.js` or similar. Investigate if there's already a glob or filter pattern; otherwise, implement a simple ignore list or regex option. Since the issue is old and no PR exists, consider discussing with maintainers on the current relevance and preferred API design.
add an option to ignore/filter files in the importer · keystonejs/keystone-classic#3690 | Good First Issue