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
Make lists sortable with ordering setting #3711
Conversation
… order now correctly updated on create
I'm confused, I'm trying to find the Vue.js component but it seems it's initialized with JQuery? |
Yes, I looked at the AdminMenu as you suggested, but that was done with jQuery nested sortable. Figured a vue component would really suit for the other part of your notes on #2355 regarding adding existing items and detaching from #3667. Happy to reconsider if you prefer it being done with Vue? |
If the feature you are adding works it's fine merging it. I'm just surprised to see it's using JQuery instead of a full Vue.js component, but like you say it can be added later on. Up to you to do the changes on this PR or on an other one later on. |
Probably another PR for the other features - not totally sure how add / move / detach items would work / look like yet |
# Conflicts: # src/OrchardCore.Modules/OrchardCore.Lists/OrchardCore.Lists.csproj # src/OrchardCore.Modules/OrchardCore.Lists/Settings/ListPartSettingsDisplayDriver.cs # src/OrchardCore.Modules/OrchardCore.Lists/Startup.cs
@Skrypt @sebastienros Fixed up some merge conflicts on this old PR. Is it wanted? |
Sure it is 😄 |
Conflicts due to Docs and Fielsets PRs that have been merged recently. |
Please solve conflicts @deanmarcussen |
# Conflicts: # src/OrchardCore.Modules/OrchardCore.Contents/Views/Content.SummaryAdmin.cshtml # src/OrchardCore.Modules/OrchardCore.Lists/Views/ListPartSettings.Edit.cshtml
@agriffard conflicts resolved. tested as it's so old this pr, but still works fine! |
Ok reviewing this one now. |
It's still using netstandard 2.0 so we can't merge this. |
@Skrypt how do you figure that? Here's the complete
|
I think I know what I did wrong then |
Ok it worked. The commits are pushed. I think it can be merged now. |
cheers @Skrypt changes LGTM. @agriffard if you feel like merging :) |
@deanmarcussen What about a démo in today's meeting? |
Why not indeed Antoine :) |
# Conflicts: # src/OrchardCore.Modules/OrchardCore.Lists/Settings/ListPartSettingsDisplayDriver.cs
@@ -72,29 +59,22 @@ public override IDisplayResult Display(ListPart listPart, BuildPartDisplayContex | |||
); | |||
} | |||
|
|||
private async Task<PagerSlim> GetPagerAsync(IUpdateModel updater, ListPart part) | |||
private async Task<PagerSlim> GetPagerAsync(BuildPartDisplayContext context) |
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.
It should be GetPagerSlimAsync and we should also have GetPagerAsync
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.
It should be GetPagerSlimAsync and we should also have GetPagerAsync
Changed to GetPagerSlimAsync
.
What did you mean by also having GetPagerAsync
? As a settings option too have the other type of pager?
This fixes #2355
Ordering is optional and configured on the last part settings
When enabled list items are sortable, when disabled they remain sorted by created date - descending