Meteor-Community-Packages / Meteor-Community-Packages/meteor-autocomplete
Template to control selected value
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 350
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
I think we need more control over the selected value. A function to transform the value based on the selected document would solve this problem. I.e match is made on Document.X but selection result is Document.Y or something more complex (like Document.X + '-' + Document.Y)
I hit this problem when writing an emoji look up using a colon : as a token. The result was ::smile: when i wanted :smile
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
No files, tests, or entry points are named. Start by tracing the autocomplete selection flow for the emoji lookup example and determine where the matched document becomes the selected value. Done means the API supports transforming the selected result without changing matching behavior, with coverage for both a single document field and a composed value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100