-
-
Notifications
You must be signed in to change notification settings - Fork 407
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 drag and drop reordering for images uploaded to how-to steps #227
Comments
When creating a how-to on the page |
@sanjuskm05 is working on this 🥳 |
@BenGamma @chrismclarke Do we have an edit feature for the "How to" and its steps? If not, i think we should address that first. Also, I was thinking can we address reordering of steps rather than drag and drop the images. 'Drag and drop' feature could be more helpful when we are creating and editing. |
Issue is there (#103) but nobody is currently assigned to it. Your call if you want to first work on images, editor or anything else. Reordering steps would also be a good feature, in the past I've used libraries like dragula but sure there are plenty of options out there so might be worth a quick bit of research. In all of these cases we're essentially just talking about ways of reordering arrays. |
thanks for the input on dragula. I will try to implement this. |
I think there might be more popular choices for react: Will leave you to experiment and see what works |
https://www.npmjs.com/package/react-beautiful-dnd seems particularly nice |
@sanjuskm05 I know you said you won't be able to help us anymore for the time being but are you gonna complete this issue or shall I de-assign you from this? |
Thanks. Please unassign it |
Thanks for the update, I see you have been unassigned and I have just added back the |
I've used Please note: We do not currently have ability on the backend for image ordering. |
merge into #939 |
Sometimes can happen that a user uploads pics in a step in the wrong order. We should enable users to move pics up and down to fix this little issue
child of #3
The text was updated successfully, but these errors were encountered: