feat: Add "Default post language" option #387
No reviewers
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#387
Loading…
Reference in a new issue
No description provided.
Delete branch "partizan/akkoma-fe:386-default-post-lang"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@floatingghost please take a look
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,
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
@ -214,2 +213,3 @@
:value="language.value"
>
{{ language }}
{{ language.value }}
ig for consistency in case we ever tweak the human-readable labels, this should use
language.key
andlangauge.label
at the appropriate places@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.
behaves as i would expect, thanks! i've fixed the merge conflict that 377 introduced and merged this via
1adef56603
@floatingghost seems like an error slipped into the merge conflict resolution;
postLanguages
still usesinterfaceLanguage
before the ISO normalisation andisoLanguage
is now unused (defined directly afterpostLangauge
)i must be stupid :)
i'll fix it
ok it should be good now (tm)
Pull request closed