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
Add heading tests and testbed #52
Conversation
✔️ Deploy Preview for monarch-ui-new ready! 🔨 Explore the source changes: e11a136 🔍 Inspect the deploy log: https://app.netlify.com/sites/monarch-ui-new/deploys/617726a8b54af7000730382a 😎 Browse the preview: https://deploy-preview-52--monarch-ui-new.netlify.app |
@falquaddoomi If you already started looking at this, hold off. Adding one more significant commit. |
@falquaddoomi ready for (re)review |
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.
Nice! I like the addition of the testbed endpoint. IIRC Sean mentioned it before, but you might be interested in Storybook, which is quite like your widget gallery but has support for injecting props, mocking external state, and other things.
Just FYI, I was able to run the tests and they all passed. There appear to be some warnings related to vuex
, but I don't think they're critical or in our power to fix.
Regarding storybook, yeah the testbed is a very "lite" version of that idea. Actually using storybook is probably overkill, since so far we don't have a lot of components, options, or developers. Perhaps in the future when the ui team gets more members or maintainers, or when/if we have more components, we can implement it. If we ever make some of these components publicly usable, that would also be a great case for implementing storybook. Not talking about the basic buttons/accordions/tooltips/etc which are not valuable to release; talking more specific widgets like genome feature viewer or something. Regarding the test errors, I don't think I'm seeing any
|
Fair point about Storybook being overkill, at least for now. I thought I'd mention it since your implementation looked similar. Here are the warnings that I saw; note that they're just warnings, not errors, and they could be specific to my machine. I'm using node v16.8.0, fyi. (I did wipe
|
Thanks for posting. Weird that I don't get that message. Looks like it might be fixed soon and we'd just have to update vuex: vuejs/vuex#2071 Though there's a good possibility we'll never even have to use vuex in this project. I might even remove it for the time being since it's pretty easy to setup again. |
Incorporates #51 (review)
innerText
totextContent
for support in jest (jsdom)