-
Notifications
You must be signed in to change notification settings - Fork 26
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
Expose syntax_style
#261
Expose syntax_style
#261
Conversation
Codecov Report
@@ Coverage Diff @@
## main #261 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 37 37
Lines 2806 2807 +1
=========================================
+ Hits 2806 2807 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Yes, otherwise every new field we add to the schema becomes a breaking change for anyone on an older version of npe2 |
Makes sense. It would be nice if the |
I can't tell if this failure is a real bug. Are we missing |
just an internet problem |
Still failing :/ |
still think it's internet... see this test: https://github.com/napari/npe2/actions/runs/3693708290/jobs/6256673381 where everything passed but codecov |
see #255 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! Just updated to fix the tests. If they all pass now, I'll look to merge tomorrow.
While working on fixing napari themes (see this zulip conversation) I noticed that some fields that are available in napari are not exposed/tested here:
icon
was unused, andsyntax_style
was not exposed. I added them to the specs and description.Also, I noticed that if you pass wrong/nonexisting keys,
npe2
does not complain. Is this intended?