github-linguist/linguist

improve Prolog vs. IDL detection (.pro files)

Open

#5,053 opened on Oct 17, 2020

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Ruby (5,166 forks)batch import
Good First IssueMisidentified Language

Repository metrics

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

Description

Apparently some .pro files are detected as Prolog, while others are given the IDL label. The latter is related with the IDL/GDL/PV-WAVE language family.

In the GDL project, all .pro files are IDL source code, while they fall in both categories according to github:

Would be great to improve consistency (i.e., so that all are detected as IDL).

Likely relevant helper info: https://github.com/blackducksoftware/ohcount/blob/master/src/parsers/idl_pvwave.rl

HTH, Sylwester (originaly reported by @EdwardEisenhauer)

Contributor guide

Research direction
Examine the language detection rules for .pro files in Linguist and the ohcount parser to improve Prolog vs IDL classification.
Tech stack
ruby
Domain
tooling
Issue type
Bug
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.
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.
Mostly clear
Prerequisites
GitRuby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60