Skip to content
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

New optional placeBefore parameter for row().child.show() #120

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

KarloX2
Copy link

@KarloX2 KarloX2 commented Feb 19, 2018

Makes it possible to control the placement of the child rows, either immediately after the parent row (which is the default), or (as a new option) immediately before the parent row. This can be specified on a per-row basis.

Makes it possible to control the placement of the child rows, either immediately after the parent row (which is the default), or (as a new option) immediately before the parent row. This can be specified on a per-row basis.
@DataTables
Copy link
Collaborator

Excellent thank you for this! Are you happy for it to be included under the MIT license?

I might sit on it for a little while, before merging it in to see if there is any other interest in it, but that's a good patch - thanks!

@KarloX2
Copy link
Author

KarloX2 commented Feb 19, 2018

Thanks. Yes, MIT license is ok, of course.

@KarloX2
Copy link
Author

KarloX2 commented Feb 19, 2018

Just a brief explanation about how I use this feature in my application:

A child row is placed before every regular data row with a message text (in a cell over the entire table width) and this message is the most important and leading piece of information for every record and is always visible. The cells/fields in the regular row beneath are logically details (like when-raised, level of importance, source of information etc.) of this message, and visibility of some of these columns can be selected, but the ("child-") message row can’t be hidden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants