ppy/osu-localisation-analyser

Issues

• Inspections for when the xmldoc comment doesn't match the text

  #37 opened 9 months ago by smoogipoo
  0

• "String can be localised" support for `SettingSourceAttribute`

  #59 opened a year ago by Joehuu
  0

• [Proposal] Category the the localization string class by folder.

  #53 opened 2 years ago by andy840119
  0

• [Proposal]Able to add the localization to all matched localization class.

  #54 opened 3 years ago by andy840119
  2

• Strings are reported to be localisable when return type is `string`

  #52 opened 3 years ago by smoogipoo
  2

• `zh-TW` is an unsupported culture code

  #44 opened 3 years ago by smoogipoo
  8

• Apostrophes not handled correctly

  #41 opened 3 years ago by peppy
  0

• Analyser for incorrect usages of `[LocalisableDescription]`

  #39 opened 3 years ago by smoogipoo
  0

• Support for automatic `LocalisableEnum` generation

  #27 opened 3 years ago by smoogipoo
  1

• Nested classes should use the top-level class for strings class name

  #32 opened 3 years ago by smoogipoo
  0

• Codefix should generate member names using full string

  #33 opened 3 years ago by smoogipoo
  0

• Change prefix via a .editorconfig option

  #28 opened 3 years ago by smoogipoo
  0

• `to-resx` command should output to a directory

  #29 opened 3 years ago by smoogipoo
  0

• Strings in attributes get hinted as localisable when it's not possible

  #25 opened 4 years ago by peppy
  0

• Visual Studio preview generates localisations immediately

  #18 opened 4 years ago by smoogipoo
  0

• License headers are not inserted into files

  #1 opened 4 years ago by smoogipoo
  0

• "Strings" class suffix should not be included in the prefix

  #3 opened 4 years ago by smoogipoo
  0

• Localisation classes should mention they're auto-generated

  #2 opened 4 years ago by smoogipoo
  0