Meteor-Community-Packages / Meteor-Community-Packages/meteor-autocomplete
support for non-collection source
Open
Nobody has claimed this yet.
question
- Dominant language
- CoffeeScript
- Stars
- 350
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Maybe i missed something in documentation , but i looks like that source have to be collection which looks really strange. Why not not allow custom array ?
Contributor guide
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.
Research direction
The issue names no files, tests, or entry points. Start by reading the package documentation and locating the source handling that currently requires a collection; define how a custom array or other non-collection source should be supplied, then document and verify the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100