-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
Core rewrite #2858
Core rewrite #2858
Conversation
It was based on a misconception on my end
Hey @jspsych/core I've added the documentation updates here that are related to the core changes. I still need to update the docs for the button plugins. I'm gonna make some new examples for those, so it may take me a little bit longer. |
@bjoluc I'm wondering if the default flexbox layout for the button response plugins is flexible enough. One of the queries that pops up on the discussion forum periodically is about arranging the buttons into a grid. I wanted to make an example like that, but it's not straightforward to implement in the new A few options:
What do you think? |
@jodeleeuw Wonderful, thanks! As for the button response flexbox layout: I think achieving different layouts with |
I get the sense from the discussion forum that arranging buttons in a grid is common enough that we should support it. Maybe I'm lacking imagination, but I can't think of a simple way to do that with |
Argh, sorry, I was thinking of |
Add `button_layout` parameter to support CSS grid
I think this might be ready to merge into |
Hey @jspsych/core,
my initial v8 work is ready 🎉 It is fully backwards compatible except for the changes mentioned in the changeset. The remaining TODOs for this PR are:
array
, but are intended to accept non-array values too. The new implementation throws an error in that case. What should we do? Update the plugins? Just remove the error? Find some other solution? I'm happy about your ideas!Once this PR is ready, we can merge it into
v8
and implement new features in separate PRs againstv8
so things keep trackable. Excited to move this forward!