microsoft / microsoft/pxt-microbit
intellisense for datalogging should not suggest columns already used in a log call
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
When you're logging columns, it would be good for Intellisense not to suggest columns already used in that log statement.
If you call something like:
datalogger.log(datalogger.createCV("compost", 1), datalogger.createCV("compost", 2), datalogger.createCV("compost", 3))
You will only get a single row with '3' as the entry for 'compost'
To Reproduce
Expected behavior
I think the already used values should be removed from intellisense.
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
Start by reproducing the datalogger.log call using repeated datalogger.createCV values and inspect the Intellisense suggestions for that statement. Trace the Intellisense and datalogger entry points involved in generating column suggestions. Done means columns already used in the log call are no longer suggested and the single-row logging behavior is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100