Skip to content

Include better debug diagnostics #4952

@armijnhemel

Description

@armijnhemel

Short Description

I am trying to find out why certain rules are not applying correctly. The current license diagnostics are not sufficient for that. Although --license-text-diagnostics includes some information I would want to see more of the internal stuff, such as the internal representation of the rule that was matched (the cleaned up version).

Possible Labels

  • new feature

Select Category

  • Enhancement
  • Add License/Copyright
  • Scan Feature
  • Packaging
  • Documentation
  • Expand Support
  • Other

Describe the Update

See short description.

How This Feature will help you/your organization

I am seeing many matches that are incorrect, or slightly incorrect, even though it seems that the correct rules are present in scancode. I want to find out why these don't match, so existing rules can be tightened, or new rules can be added.

Possible Solution/Implementation Details

I would like to see a feature where I can dump the internal representation of the license text that was matched. I am thinking of a representation of the license text, that has been cleaned up (whitespace, punctuation, and so on), so I can see what was matched against.

Example/Links if Any

Can you help with this Feature

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions