Skip to content

classify XML files with .ncl extension as XML#4187

Merged
lildude merged 1 commit intogithub-linguist:masterfrom
smola:xml-ncl
Jul 21, 2018
Merged

classify XML files with .ncl extension as XML#4187
lildude merged 1 commit intogithub-linguist:masterfrom
smola:xml-ncl

Conversation

@smola
Copy link
Contributor

@smola smola commented Jul 9, 2018

Description

When NCL support was added (see #2440), XML files with .ncl extension were classified as Text. This PR moves them to XML adding a simple heuristic.

Tested on https://gist.github.com/pchaigno/2478bc86dd831382bfba by @pchaigno and, at least for the files that still exist today, this seems to be working correctly.
XML files with .ncl extensions were being classified as text.

Checklist:

  • I am fixing a misclassified language
    • I have included a new sample for the misclassified language:
    • I have included a change to the heuristics to distinguish my language from others using the same extension.

Copy link
Contributor

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @smola for fixing this!

We did not add a test in test_heuristics.rb for the .ncl heuristic rules at the time; could you add one now?

XML files with .ncl extensions were being classified as text.
@smola
Copy link
Contributor Author

smola commented Jul 9, 2018

👍 Done.

Copy link
Contributor

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect! Thanks!

@pchaigno pchaigno requested a review from lildude July 21, 2018 09:27
@lildude lildude merged commit c5c7bd3 into github-linguist:master Jul 21, 2018
@github-linguist github-linguist locked as resolved and limited conversation to collaborators Jun 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants