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

`@spec import()` considers import as `keyword.control.elixir`

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
elixir
Domain
tooling

Research direction

Start by inspecting the Elixir syntax-highlighting grammar and the rule that classifies import inside @spec. Reproduce the provided snippet in TextMate or Sublime Text and compare its highlighting with the expected function-spec text. Done means import in @spec is no longer highlighted as keyword.control.elixir.

Written by the indexing model from the issue text.

Description

Given this code:

  @spec import(Plug.Conn.t(), map()) :: Plug.Conn.t()
  def import(conn, attrs) do
    # implementation here
  end

The syntax highlighter treats the function name in @spec import as an import keyword.

image

Expects @spec import to be treated as a part of the function spec. As in the screenshot above, the text should be in white rather than red.

Dominant language
Python
Stars
262
Forks
65
PR merge metrics
No merged PRs in 30d

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 elixir-editors/elixir-tmbundle

All issues in elixir-editors/elixir-tmbundle

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.