Reduce "shortcut already assigned" error to a debug message

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
backend

Research direction

Start by reproducing the shortcut-already-assigned case in Node and trace where the error is emitted. Identify the existing logging entry point and verify that the condition reports at debug or info level rather than as an error.

Written by the indexing model from the issue text.

Description

area:ff-expert size:XS task
Description

Node unnecessarily outputs errors for something that should only be an info or debug message
Image

Epic/Story

No response

Dominant language
JavaScript
Stars
5
Forks
5
Avg merge
1d 5m
Merged PRs (30d)
29

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FlowFuse/nr-assistant

All issues in FlowFuse/nr-assistant

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.