Detect encoding issues and warn user

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cli

Research direction

Start by locating the code that reads or converts .properties files using the configured encoding, then inspect any nearby tests. Confirm how characters unavailable in the selected encoding are handled and add coverage for the warning; done means affected files produce a clear warning without changing valid conversions.

Written by the indexing model from the issue text.

Description

module/ui5-builder

Is your feature request related to a problem? Please describe.

When using the wrong configuration for *.properties file source encoding, or when using an invalid character or one that is not available for the desired encoding, the user should be warned.

Describe the solution you'd like

When a character can't be found in the configured encoding's code page, a warning should be logged, indicating a potential encoding issue, either with the file or through incorrect configuration.

Describe alternatives you've considered

Additional context

Dominant language
JavaScript
Stars
511
Forks
83
Avg merge
1d 5h
Merged PRs (30d)
55

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.

More from UI5/cli

All issues in UI5/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.