jakethedev / noish Goto Github PK

#!/usr/bin/env node

Currently, noish is built specifically to only handle open source project issue listing. This issue is a bookmark saying I've thought about it and decided to not set up auth handling because yagni.

If this gets 10+ unique positive reactions, I'll set up auth so orgs and private repos can use it via https auth.
Fully open to good clean PRs on this as long as you use axios, I just won't need it and I'm building this for me.

https://www.npmjs.com/package/colors

It has 0 dependencies and does magic right on the string prototype, which would be janky if noish could be a lib, but it really never should be

Currently, that's all it gets, even from the microsoft/vscode repo

This would be super handy. I think the cache has what's needed, no idea, but it should be easy with 1.0 out

Part 1: Set up mocha tests
Part 2: When access opens, use https://github.com/actions/npm

Throws an exception related to git remote?

Should be able to print a full issue nicely by providing an id.

>> cd gitrepo;
>> noish -i 5;
-- Print full issue by id --
Should be able to print a full iss[cut for brevity]

This should be visible with base nish functionality

This was built for github, but it would be cool to have it work with bitbucket as well.

Gitlab support would be neat,

Should be an easy fix for this, pretty annoying to have to update .git/config for certain repositories just to get the public issues

Should be able to search whole text of issues, case insensitive, and get a list of "ID: Title, snippet of initial summary"

>> cd gitrepo;
>> noish -s Local
-- 1 issue found --
#4: Searching local cache
    Should be able to search whole text of iss...
>> 

By default, only list and search open issues - we should have an option to list closed issues

>> noish -s Closed
-- 1 issue found --
#6 List closed issues: By default...

>> noish -s Closed -c
-- 1 closed issue found --
#2 Closed Issue: Test closed issue. Shouldn't be visible unle...
>>

This mostly happens on private repos since auth is not going to be a feature here, so that should be part of the output - "ensure you're working on a public repo" would be adequate

On update, noish should save off the full json response somewhere. Thinking ~/.noish/uname/repo.json - then search is 100% local.

Should be all we need to fix npm i -g noish, currently installing it won't link it to the node bin folder - the http-server repo works great though, and the only difference seems to be folder structure

Test closed issue. Shouldn't be visible normally unless asked for