Skip to content

Conversation

@DarkDefender
Copy link
Contributor

@DarkDefender DarkDefender commented Jun 9, 2024

For example, running pytest -l will error out as Beeref would try to parse -l as a log level flag. Now we no longer try to blindly parse flags when including the Beeref commandline parser.

I ran into this when working on the other PR.

For example, running "pytest -l" will error out as Beeref would try to
parse "-l" as a log level flag. Now we no longer try to blindly parse
flags when including the Beeref commandline parser.
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.94%. Comparing base (caed5c3) to head (60d79d4).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   97.94%   97.94%           
=======================================
  Files          33       33           
  Lines        4376     4376           
=======================================
  Hits         4286     4286           
  Misses         90       90           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

In beeref/selection.py and beeref/view.py the commandline arg parse
object would be created on import.

Previously this would lead to the arg parse object being out of date
when checking it.

Now we don't recreate the arg parse helper object and instead make sure
that it is static.
@DarkDefender
Copy link
Contributor Author

Just to clarify that the tests are passing on my machine at least.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants