Skip to content
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

Fix default extension_name and validation #175

Merged
merged 1 commit into from
Jan 29, 2020

Conversation

jtpio
Copy link
Member

@jtpio jtpio commented Jan 28, 2020

Trying out the ExtensionApp PR in voila, it looks like the default value for extension_name was not picking up name.

Also the validation should extract the value from the proposal.

@jtpio jtpio force-pushed the default-extension-name branch from 70a4527 to 0815d92 Compare January 28, 2020 11:54
@jtpio jtpio mentioned this pull request Jan 28, 2020
@vidartf
Copy link
Member

vidartf commented Jan 29, 2020

I don't get why CI is failing...

@jtpio
Copy link
Member Author

jtpio commented Jan 29, 2020

Especially with this change: #176

@kevin-bates
Copy link
Member

Yeah, I suspect there's an issue in pytest. I see that 5.3.4 was built solely to revert a regression introduced in 5.3.3 and see that 5.3.3 (built just a few days prior to 5.3.4) appears to have other issues where folks are needing to pin to 5.3.2.

Not sure why this isn't an issue for the Travis and Appveyor CI suites though.

Since I just submitted #177, and its build-related anyway, I'm going to add the pin to 5.3.2 in that PR to see how it goes.

@Zsailer
Copy link
Member

Zsailer commented Jan 29, 2020

Looks like pinning pytest worked in #177, thanks @kevin-bates.

@Zsailer Zsailer merged commit 1c8a3b8 into jupyter-server:master Jan 29, 2020
@jtpio jtpio deleted the default-extension-name branch January 29, 2020 19:58
Zsailer added a commit to Zsailer/jupyter_server that referenced this pull request Nov 18, 2022
* add geojson renderer

* add version

* Bump to 0.13.7
hMED22 pushed a commit to hMED22/jupyter_server that referenced this pull request Jan 23, 2023
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.

4 participants