Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / wise-introvert/deepsearchjs issues and pull requests

#22 - Search across values.

Issue - State: open - Opened by wise-introvert almost 2 years ago
Labels: enhancement

#21 - Implement hashtables.

Issue - State: open - Opened by wise-introvert almost 2 years ago
Labels: enhancement

#20 - ci/cd: grunt integration in publish workflow

Pull Request - State: closed - Opened by wise-introvert almost 2 years ago

#19 - feat: grunt task runner

Pull Request - State: closed - Opened by wise-introvert almost 2 years ago

#18 - feat: grunt task runner

Pull Request - State: closed - Opened by wise-introvert almost 2 years ago

#17 - Prefix tree

Issue - State: closed - Opened by wise-introvert about 2 years ago

#15 - Also, a word of advice: Don't export utility functions that are not central to the purpose of your module. Specifically, isArray and isObject should be kept private. Users already have plenty of other options for that sort of thing, and when (not if!) they depend on your implementations you lose the flexibility of changing them should the need arise.

Issue - State: closed - Opened by wise-introvert about 2 years ago

#14 - Rather than walking the entire object to get all keys up front, consider implementing the search logic using a generator function, where each `yield` returns a [key, value] entry (similar to Object.entries()). This will allow callers to control how many results they get and at what velocity. (E.g. if caller only needs the first result, there's no reason to crawl the whole object. E.g. if caller wants to paginate results or pause scanning while waiting for user input or whatever). 'Will be a much more useful and performant.

Issue - State: closed - Opened by wise-introvert about 2 years ago

#13 - Move the line that creates regex outside of the keys.filter() method. That way you only create regex once rather than N times (N = # of keys).

Issue - State: closed - Opened by wise-introvert about 2 years ago

#12 - Maybe also consider allowing query to be a function that takes (keyPath, value) as arguments and returns true | false to indicate whether the entry should be included in the results. (Generally speaking regex-based query systems tend to prove problematic beyond a certain level of complexity, at which point users will want to provide their own filtering logic.)

Issue - State: closed - Opened by wise-introvert about 2 years ago

#11 - Consider allowing query to be a RegEx or string. Gives callers more control over which keys are searched. (Useful for finding results in groups of keys. E.g. /address_.*/

Issue - State: closed - Opened by wise-introvert about 2 years ago

#10 - Need examples showing more complex query cases. A single example with a query of "p" tells me virtually nothing about how I might expect to use this module.

Issue - State: closed - Opened by wise-introvert about 2 years ago

#9 - refactor: feedback from reddit user

Issue - State: closed - Opened by wise-introvert about 2 years ago

#8 - tests: add more tests

Pull Request - State: closed - Opened by wise-introvert about 2 years ago

#7 - docs: add jsdoc generated using chatgpt

Pull Request - State: closed - Opened by wise-introvert about 2 years ago

#6 - docs: improve documentation

Issue - State: closed - Opened by wise-introvert about 2 years ago - 1 comment

#5 - build: decrease package build size

Issue - State: closed - Opened by wise-introvert about 2 years ago
Labels: enhancement

#4 - feat: Search across values??

Issue - State: closed - Opened by wise-introvert about 2 years ago
Labels: enhancement

#3 - feat: Add a third parameter to the function to customise the search configurations ( leaf-node results only, etc... )

Issue - State: closed - Opened by wise-introvert about 2 years ago - 1 comment
Labels: enhancement

#2 - feat: Optimize search algorithm to handle oversized datasets

Issue - State: closed - Opened by wise-introvert about 2 years ago - 2 comments
Labels: enhancement

#1 - ci/cd: Automate versioning and releases

Issue - State: closed - Opened by wise-introvert about 2 years ago - 2 comments
Labels: enhancement