feat: Add "Default post language" option #387

Closed
partizan wants to merge 0 commits from partizan/akkoma-fe:386-default-post-lang into develop
First-time contributor

I have added setting for default posting option.

I changed direct import of iso6391 into composable usePostLanguageOptions, to avoid duplicating code.

Please advise where to best put this composable, i put it into src/lib for now.

Refs #386

I have added setting for default posting option. I changed direct import of iso6391 into composable usePostLanguageOptions, to avoid duplicating code. Please advise where to best put this composable, i put it into src/lib for now. Refs #386
partizan added 1 commit 2024-04-20 13:11:31 +00:00
feat: Add "Default post language" option
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
042e8c78dc
Refs #386
Author
First-time contributor

@floatingghost please take a look

@floatingghost please take a look
Oneric reviewed 2024-05-13 01:33:04 +00:00
Oneric left a comment
Member

sans one small nit, seems good afaict

this will introduce or be affected by a small merge conflict with #377, but should be easy to fix regardless of what is merged first

sans one small nit, seems good afaict this will introduce or be affected by a small merge conflict with #377, but should be easy to fix regardless of what is merged first
@ -165,3 +174,3 @@
mediaDescriptions: this.statusMediaDescriptions || {},
visibility: this.statusScope || this.suggestedVisibility(),
language: this.statusLanguage || interfaceLanguage,
language: this.statusLanguage || postLanguage,
Member

note: this doesn’t actually work for edit dialogues (always falls back to interface/defaultPostLanguage), but that’s a pre-existing issue so no need to worry about for this patch

note: this doesn’t actually work for edit dialogues (always falls back to interface/defaultPostLanguage), but that’s a pre-existing issue so no need to worry about for this patch
partizan marked this conversation as resolved
@ -214,2 +213,3 @@
:value="language.value"
>
{{ language }}
{{ language.value }}
Member

ig for consistency in case we ever tweak the human-readable labels, this should use language.key and langauge.label at the appropriate places

ig for consistency in case we ever tweak the human-readable labels, this should use `language.key` and `langauge.label` at the appropriate places
partizan marked this conversation as resolved
partizan added 1 commit 2024-05-13 13:14:21 +00:00
fix: Use label and key for options
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
57beea6a0d
Author
First-time contributor

@Oneric maybe merge #377 first, so i can handle that change here.

And i can look into into edit dialog bug after we merge this.

@Oneric maybe merge #377 first, so i can handle that change here. And i can look into into edit dialog bug after we merge this.
Oneric approved these changes 2024-05-13 17:41:46 +00:00

behaves as i would expect, thanks! i've fixed the merge conflict that 377 introduced and merged this via 1adef56603

behaves as i would expect, thanks! i've fixed the merge conflict that 377 introduced and merged this via 1adef56603929997fb0108e92f6eb39ed88b30fb
floatingghost closed this pull request 2024-05-28 02:22:18 +00:00
Member

@floatingghost seems like an error slipped into the merge conflict resolution; postLanguages still uses interfaceLanguage before the ISO normalisation and isoLanguage is now unused (defined directly after postLangauge)

@floatingghost seems like an error slipped into the merge conflict resolution; `postLanguages` still uses `interfaceLanguage` before the ISO normalisation and `isoLanguage` is now unused (defined directly _after_ `postLangauge`)

i must be stupid :)

i'll fix it

i must be stupid :) i'll fix it

ok it should be good now (tm)

ok it should be good now (tm)
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful

Pull request closed

Sign in to join this conversation.
No description provided.