-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Not possible to write custom plugins anymore #4406
Comments
This could have been caught if we had any cypress tests for the plugins frontend. Not sure we wouldn't have just ignored the failing test then though. 😬 |
I'm pretty sure this was a wrong branch after running the |
Same, waiting for Karl to confirm he can re-reproduce. About Cypress tests for Plugins: sounds like a good idea to me, doing this with the default source plugin. I'll do this. |
I've deprioritized cypress tests for now, since there's a big batch of plugin frontend work that will land on our plate in the near future, but probably not next sprint (stuff like improving the editor, making failures more interactive (no need to reload), changing the URL if you have a plugin open, testing environment, etc), and it might make sense to combine this work. |
Verified, this seems to have been exactly the scenario @Twixes suggested. Sorry for the noise! |
Bug description
#4371 added a new capabilities column. After it it's not possible to start creating a new plugin anymore
Expected behavior
Should be possible to add a new plugin
How to reproduce
Environment
Additional context
cc @neilkakkar for this bug.
It's worth creating a cypress e2e test which goes through this flow.
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: