asgardeo/javascript

chore: add `Slovenian - sl-SI` language support

Open

#200 opened on Oct 5, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (65 forks)auto 404
@asgardeo/i18nComplexity/LowType/Improvementaccessibilitygood first issue

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

Current Limitation

Currently, the Asgardeo JavaScript SDK does not have support for Slovenian (Slovenščina - sl-SI). Users who prefer Slovenian will not see UI components translated, limiting accessibility and localization for Slovenian-speaking users in Slovenia and globally.

[!Important] Contributors for this task should be native Slovenian speakers or have professional fluency to ensure accurate, culturally appropriate translations.

Suggested Improvement

Add Slovenian (sl-SI) language support to the @asgardeo/i18n package.

Implementation Plan:

  1. Create a new locale file:

    Follow https://github.com/asgardeo/javascript/blob/main/CONTRIBUTING.md#contributing-to-the-internalization-i18n-package

  2. Add documentation for usage:

Please select the package issue is related to

@asgardeo/i18n

Version

current

Reporter Checklist

  • I have searched the existing issues and this is not a duplicate.
  • I have provided all the necessary information.
  • I have verified the improvement is not available in the latest version of the package.

Contributor guide

Research direction
Create a new locale file for Slovenian (sl SI) following the i18n contribution guide, then update the documentation to include this new language.
Tech stack
typescript
Domain
internationalizationlocalizationdocumentation
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitFamiliarity with i18n concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90