Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

✨ Snippets

Open
#1,623 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift
Domain
desktop, tooling

Research direction

The issue names CodeEditSourceEditor completion service and menu, plus wildcard support, as blockers, but gives no implementation files or tests. Start by reading those CodeEditSourceEditor areas and clarify the scope of the snippet library, insertion, completion, wildcard, and extension APIs. Done means the listed snippet creation, cursor insertion, scoped completion, wildcard, extension, and overlay behavior works.

Written by the indexing model from the issue text.

Description

enhancement extensions snippets toolbar
Description

Users should be able to make and insert code snippets to insert into their open file at the current cursor position.

Snippets should be able to support wildcards.

Snippets should have a completion, so when a set of characters are typed within a given scope, it will suggest the snippet without having to open the Snippets overlay.

Additionally, extensions should be able to add snippets.

We might include this in a larger library feature at a later point in time.

The snippets/library overlay could be accessed by a keyboard shortcut and/or a plus icon button in the toolbar.

[!NOTE]
There may require additional functionality to be build into CodeEditSourceEditor to support some of this, so we may need to do some of this after this is done.

Blockers
  • CodeEditSourceEditor completion service and menu
  • CodeEditSourceEditor wildcard support
Screenshots
Screenshot 2024-03-14 at 2 34 06 PM image Screenshot 2024-03-14 at 2 36 13 PM
Dominant language
Swift
Stars
23.1k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Getting set up

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 CodeEditApp/CodeEdit

All issues in CodeEditApp/CodeEdit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.