#372 allow sortable(false) on fields in list view#984
#372 allow sortable(false) on fields in list view#984RichardBradley wants to merge 1 commit intomarmelab:masterfrom
Conversation
|
Taking a step back, why is |
|
Please update |
|
.disableSort(true), Not work in my panel, why? |
Because this enhancement has not yet been implemented. |
@fzaninotto Is there a guide on how best to do this? I'll make the changes to I suppose I should publish it locally somehow (how?) and then have my local |
9f41a08 to
8c2215e
Compare
|
OK, I have updated this pull request to include the necessary changes to This now depends on marmelab/admin-config#65 -- please merge and release that first, or this will fail. I have bumped the I have not included changes to |
|
(The CI build has failed because it cannot find the not-yet-published version of |
|
I have changed the syntax from the proposed "disabledSort(true)" to " |
| @@ -5,21 +5,21 @@ A field is the representation of a property of an entity. | |||
| * [General Field Settings](#general-field-settings) | |||
There was a problem hiding this comment.
please revert these changes, they are not related to this PR, and break the ng-admin book on GitBook (i.e. the official doc)
There was a problem hiding this comment.
OK, will do.
The links are currently broken on GitHub, see e.g. https://github.com/marmelab/ng-admin/blob/master/doc/reference/Field.md#-date-field-type
They do work on the "GitBook" version, you're right: http://ng-admin-book.marmelab.com/doc/reference/Field.html#-date-field-type
It's a shame that the two differ. I hadn't spotted the "GitBook" version; I'd been referring to the documentation on GItHub directly up until now. If the GitBook version is the official one, it should win, of course.
8c2215e to
b095fe6
Compare
|
I have pushed a new version with the requested changes (and rebased to account for other changes in the meantime). |
|
This PR is OK, just needs rebasing |
|
Superseded by #1260 |
Fixes #372
(UPDATE: please ignore the rest of this comment, it refers to an old version of this PR. Jump straight to the comment starting "OK, I have updated this pull request to include the necessary changes")
As discussed on that thread, this PR is much easier if I don't have to also modify
admin-config.However, it does look rather out of place next to all the fields with function getters & setters, so maybe a version which spans the two respositories would be better.
This version works for me though.
(Another benefit of the getter/setter approach is that it allows a "builder" style. This version is awkward to use:
whereas the getter/setter version would look like
)