Skip to content

Conversation

@AlexVelezLl
Copy link
Member

Summary

Fixes an incorrect reference to channelLanguageExists on the showLanguageDropdown computed property. This meant that when channelLanguageExists.value was false, the language dropdown was not shown, but the publish button still required a value, making the publish modal unusable.

Before

Grabacion.de.pantalla.2025-12-11.a.la.s.9.18.59.a.m.mov

After

Grabacion.de.pantalla.2025-12-11.a.la.s.9.20.00.a.m.mov

Reviewer guidance

This showLanguageDropdown is a migration from the old publish modal. When creating the new publish side panel, this difference was overlooked.

@AlexVelezLl AlexVelezLl requested a review from rtibbles December 11, 2025 14:21
@rtibbles rtibbles self-assigned this Dec 16, 2025
Copy link
Member

@rtibbles rtibbles left a comment

Choose a reason for hiding this comment

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

@AlexVelezLl and I had a quick chat on Slack - no concerns about the bug fix, but @AlexVelezLl is going to do a little bit of code clean up of the pre-existing code before we merge.

@AlexVelezLl AlexVelezLl changed the title Fix no language select on publish side panel Refactor publish side panel Dec 17, 2025
@AlexVelezLl AlexVelezLl force-pushed the fix-no-language-select branch from 9498094 to 63eef8c Compare December 18, 2025 15:24
@AlexVelezLl
Copy link
Member Author

Noting that currently the invalid language message is not shown because of this bug in KDS, once fixed in KDS, it will be fixed automatically here.

@AlexVelezLl AlexVelezLl force-pushed the fix-no-language-select branch from 63eef8c to 44f14d5 Compare December 18, 2025 19:25
Copy link
Member

@rtibbles rtibbles left a comment

Choose a reason for hiding this comment

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

Tests provide good coverage, manual testing checks out, and the code read through makes sense.

Just one comment about the slightly confusing value.value, but not a blocker.

language.value.value &&
language.value.value !== currentChannel.value?.language
) {
if (newChannelLanguage.value.value !== currentChannel.value.language) {
Copy link
Member

Choose a reason for hiding this comment

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

I can see now that this is coming from the language options for a dropdown - I must admit the "double value" reference here was incredibly confusing for a while. May be worth a code comment to save others the mental working through to understand why this is like this.

@AlexVelezLl AlexVelezLl force-pushed the fix-no-language-select branch from 44f14d5 to 1e372fe Compare December 19, 2025 00:26
@AlexVelezLl
Copy link
Member Author

Thanks @rtibbles!

@AlexVelezLl AlexVelezLl merged commit a548354 into learningequality:unstable Dec 19, 2025
13 checks passed
@AlexVelezLl AlexVelezLl deleted the fix-no-language-select branch December 19, 2025 00:27
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