Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Exact matcher to detect OFL with a reserved font name #546

Merged
merged 2 commits into from Apr 7, 2022

Conversation

saltcandy123
Copy link
Contributor

This pull request fixes issue #523.

The solution is to expand copyright regex to include the line that mentions a reserved font name, as mentioned on the issue.

@welcome
Copy link

welcome bot commented Apr 7, 2022

Welcome! Congrats on your first pull request to Licensee. If you haven't already, please be sure to check out the contributing guidelines.

In SIL OFL 1.1, copyright notice may be two lines to include
a reserved font name. This change covers that case and enables
Exact matcher to detect such licenses.
it took me a few mins to convince myself the copyright matcher test was testing the right thing
this clarifies

matches copyright fully = no_license
copyright with any other text (license or arbitrary) = nil (bc it's the copyright matcher; other matcher would obtain the license and nil respectively)
@mlinksva mlinksva force-pushed the add-copyright-fontname-regex branch from a9a3f5f to 654d84b Compare April 7, 2022 17:25
Copy link
Contributor

@mlinksva mlinksva left a comment

Choose a reason for hiding this comment

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

Thanks! Works as suggested. Added an additional test to help me understand what's going on when I look in the future.

@mlinksva mlinksva merged commit ba9913e into licensee:master Apr 7, 2022
@welcome
Copy link

welcome bot commented Apr 7, 2022

Congrats on getting your first pull request to Licensee merged! Without amazing humans like you submitting pull requests, we couldn’t run this project. You rock! 🎉

If you're interested in tackling another bug or feature, take a look at the open issues, especially those labeled help wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants