Skip to content
This repository has been archived by the owner on Jan 19, 2025. It is now read-only.

fix: incorrect pnames #527

Merged

Conversation

lars-reimann
Copy link
Member

Closes #525.

Summary of Changes

Add missing slashes to the created pname properties.

Testing Instructions

  1. Run
cd package-parser
poetry run parse-package api -p package_parser -s package_parser -o out
  1. Check the pname properties.

@lars-reimann lars-reimann linked an issue May 29, 2022 that may be closed by this pull request
@github-actions
Copy link

MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ CREDENTIALS secretlint yes no 3.5s
✅ GIT git_diff yes no 0.01s
✅ PYTHON black 1 0 0 0.4s
✅ PYTHON isort 1 0 0 0.17s
✅ PYTHON mypy 1 0 5.34s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

@lars-reimann lars-reimann merged commit d84eecd into main May 29, 2022
@lars-reimann lars-reimann deleted the 525-incorrect-pname-properties-created-by-api-command branch May 29, 2022 15:42
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.

Incorrect pname properties created by api command
1 participant