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

refactor: move column selector from form to table #363

Closed
wants to merge 1 commit into from

Conversation

b1rger
Copy link
Contributor

@b1rger b1rger commented Oct 18, 2023

Closes: #173

@b1rger b1rger marked this pull request as ready for review October 18, 2023 15:29
@b1rger b1rger force-pushed the birger/173-addcol branch from 63701a7 to 317d7ed Compare October 19, 2023 10:18
This commit changes the way the `column_selector` is set up. Up until
now, it was a simple select input, that could only be used in
conjunction with an existing form. That meant, that the colums selector
had to be places at a position away from the actual table.
Now the column selector is its own form, therefore it can be places
whereever we want it. Also it is not a templatetag anymore, but a simple
partial template that has to be included with {% include ... %}.
The downside is, that we might now have multiple forms sending get
parameters - this is where the new "form_get_hidden.html" template comes
in. It adds existing get parameters to hidden fields in the form, that
way multiple forms don't get in each others way.

Closes: #173
@b1rger b1rger marked this pull request as draft November 23, 2023 10:35
@b1rger b1rger closed this Feb 14, 2024
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.

listview: move the "additional columns" dropdown near the table
1 participant