NativeScript / NativeScript/plugins

[@nativescript/localize + more] Better Tutorials for these plugins [Enhancement]

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
206
Forks
123
Avg merge
2d 1h
Merged PRs (30d)
1

Description

I'm used to the old version of Localize but there's no step by step documentation on how to set it up via the plugins. The demo files really don't help since they don't have the same structure as a typical project.

I'm used to this in my typescript:
import { NativeScriptLocalizeModule } from 'nativescript-localize/angular'; // added to app.module

import localize from 'nativescript-localize'; // added to component where it's used
const textString = localize('@@Translated_Text');

But now it's to be used like a pipe? Can I still use it in the Typescript?

Is the en.default now a *.js file? I was using a *.json?

Just some clarification would be awesome here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the plugin demo files and the setup examples referenced in the issue, including app.module, the TypeScript usage, and the en.default file format. Clarify whether the plugin is used as a pipe or from TypeScript, and document the current setup in a typical project structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
documentation, localization
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.