Skip to content

Apply home current language to terms page#637

Open
goodolcuppa wants to merge 4 commits into
LuteOrg:developfrom
goodolcuppa:issue_326_apply_home_current_language_to_terms_page
Open

Apply home current language to terms page#637
goodolcuppa wants to merge 4 commits into
LuteOrg:developfrom
goodolcuppa:issue_326_apply_home_current_language_to_terms_page

Conversation

@goodolcuppa

@goodolcuppa goodolcuppa commented Sep 14, 2025

Copy link
Copy Markdown
Contributor

Applying the current language filter from home page to the terms page

Closes #326

Uses the same value as home for the terms language filter. Changing the value on the terms page will not update the stored value, so on refresh, this will revert back to whichever value is set on the home page

@jzohrab

jzohrab commented Sep 30, 2025

Copy link
Copy Markdown
Collaborator

Sorry for the delay! (You know why) Initial read through: this looks very clean, I just have to try it out (assigning to me to do so, when I am able)

on refresh, this will revert back to whichever value is set on the home page

This makes sense, and it prevents people from inadvertently changing their default language selection.

Thank you very much @goodolcuppa , and again apologies for the delay.

@jzohrab jzohrab self-assigned this Sep 30, 2025
@jzohrab jzohrab added this to Lute-v3 Sep 30, 2025
@jzohrab jzohrab moved this to In Progress in Lute-v3 Sep 30, 2025
@jzohrab

jzohrab commented Sep 30, 2025

Copy link
Copy Markdown
Collaborator

@goodolcuppa - small lint error. I'll re-run the PR to check the base-ci, it should be fine.

@jzohrab

jzohrab commented Apr 22, 2026

Copy link
Copy Markdown
Collaborator

Hi again @goodolcuppa -- sorry for falling off this, I've had some medical issues. The CI logs aren't available for this anymore, so I'm not sure what went wrong. The develop branch has updated a little bit since you pushed this, perhaps you could merge the develop branch into this work and repush, and we'll see where we're at.

@jzohrab jzohrab assigned goodolcuppa and unassigned jzohrab Apr 22, 2026
@jzohrab

jzohrab commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Thanks @goodolcuppa for reactivating the code, CI is running now and we'll see how it goes. Did you have other tweaks you wanted to make to this PR, or do you think it's all good to go? Cheers!

edit: just the lint failure to be cleared up so far:

************* Module lute.term.routes
lute/term/routes.py (018): Unused Language imported from lute.models.language (W0611 unused-import)

@goodolcuppa

Copy link
Copy Markdown
Contributor Author

It should be all good to go now, thanks

@jzohrab jzohrab left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @goodolcuppa -- I just added a couple of questions for you. Cheers!

let update_filter_storage = function() {
const store = {
filtDisplay: $('#filterControls').css('display'),
filtLanguage: $('#filtLanguage').val(),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious, why is this line no longer needed? We're not using storage for the language?

dropdown.val(current_language_id);
const language_count = $("#filtLanguage option").length;
if (language_count == 1) {
dropdown.css("display", "none");

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it be hidden if there's only one language? I think it's ok to leave it. Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants