github-linguist/linguist

[Language Addition] BBCode

Open

#7,134 opened on Nov 21, 2024

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Ruby (5,166 forks)batch import
Add LanguageGood First Issue

Repository metrics

Stars
 (13,466 stars)
PR merge metrics
 (Avg merge 102d 5h) (19 merged PRs in 30d)

Description

This replaces @janmm14's github.com/github-linguist/linguist/issues/3516:

Please see the guidelines to add support for a new language to Linguist. If bbcode meets the requirement on in-the-wild usage, don't hesitate to open a pull request.

Language Name

BBCode

URL Of Example Repository

Because BBCode is utilised extensively across phpBB and vBulletin forums, its primary use case is in code snippets, like gist.github.com/betaveros/48588f5443ea664e3912/6d2a86a3d426a2f94b8b1d2671fa572fc3119e2c.

However, because the language can also be defined inline, with CommonMark's ~~~CSV equivalent to a <pre><code>, its absence causes github/markup/issues/1851.

URL Of Syntax-Highlighting Grammar

Most Popular Extensions

.BBCode would the applicable extension, because none have been standardised.

Detected Language

Currently, text/plain.

Contributor guide

Research direction
Follow the guidelines in CONTRIBUTING.md to add BBCode language support to Linguist, including adding the language definition and its extensions to the languages.yml file, and optionally adding a grammar for syntax highlighting.
Tech stack
ruby
Domain
developer experiencebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
GitRuby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80