fix: Correct script entry point for ixbrlparse
#44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
@daizutabi Thanks for this - good spot. I've added some tests to ensure that it's working properly. |
Member
|
Thanks for your contributions @daizutabi - the two PRs are now available in version 0.11.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses an issue where the
ixbrlparsecommand would fail after package installation due to an incorrect entry point definition inpyproject.toml.The entry point was incorrectly pointing to
ixbrlparse.cli:ixbrlparse, which is a non-existent function.This has been corrected to point to the proper
ixbrlparse.cli:ixbrlparse_clifunction, ensuring that the command-line interface runs as intended.