nim-works/nimskull

Dedicated VSCode Extension

Open

#447 opened on Oct 9, 2022

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Nim (39 forks)auto 404
good first issue

Repository metrics

Stars
 (346 stars)
PR merge metrics
 (PR metrics pending)

Description

Many people use VSCode or the like. At present most can make do with the Saem's Nim extension for Nimskull. Things are starting to diverge, however.

Roughly what needs to happen:

  • start a new repo for the new extension (we can move it to the Nimskull org later)
  • do some renaming/clean-up
  • get it on various marketplaces
  • link it into various docs
  • support cyo and whatever other file extensions/tools are required

Then the it can evolve over time.

Contributor guide

Research direction
Create a new repository for the extension, copy and rename files from the existing Nim extension, configure package.json for Nimskull, and publish to VSCode marketplace.
Tech stack
None
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNim
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70