vmware / vmware/singleton

[BUG] [C# Client]Can't get component list by GetComponentList() and locale list by GetLocaleList() in IReleaseMessages

Open
#930 1 comment 0 reactions 1 assignee View on GitHub

@jin-jasper is already working on this.

Since Dec 18, 2020.

area/c#-client kind/bug priority/medium
Dominant language
Java
Stars
72
Forks
69
Avg merge
23h 32m
Merged PRs (30d)
4

Description

Describe the bug
In offline mode:Can't get component list by GetComponentList() and locale list by GetLocaleList() in IReleaseMessages
Mode: Offline External Remote, Offline Internal Resx, Offline Internal Properties, Offline Internal DotNet
In mixed modes: only the online's Component List and locale List are displayed
Mode:Online With Offline Internal, Online With Offline External

To Reproduce
Steps to reproduce the behavior:
1.(The locale 'ru' only exist in offline bundle)
Such as Offline External Remote:
offline_resources_base_url: http://127.0.0.1:8094/l10ntest/CSharpClient/
l10n_version: 1.0.9
default_locale: de-DE
source_locale: en-US
default_resource_format: bundle, external
components:

  • name: about
  • name: index
  • name: contact
  • name: common
  • name: RESX
  1. PM = Utiloffline_disk.Messages()
    Translation.SetCurrentLocale("ru");
    String result1 = Translation.GetString("RESX", "RESX.ARGUMENT");
  2. List componentlist = PM.GetComponentList();
    String result2 = Common.ParseListStringContent(componentlist)
  3. List localelist = PM.GetLocaleList();
    String result3 = Common.ParseListStringContent(localelist)

Actual behavior
In offline mode: the result2 and result3 are empty
In mixed modes: only the online's Component List and locale List are displayed,not display the locale or component that only exist in offline bundle
Expected behavior
In offline mode: the result2 should be component list and result3 should be locale list
In mixed modes: all component list and locale list in online and offline are displayed

Screenshots
Such as Offline External Remote
image

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.