fix: japanese parenthesis

[benbenben2]

What

added parenthesis that can be found in Japan as separator and parenthesis to extract the ingredients

Screenshot

Before

After

Related issue(s) and discussion

• Fixes Japanese full width parenthesis not recognised #8345

[codecov-commenter]

Codecov Report

Merging #8381 (5c5fbd1) into main (d9d9c87) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #8381      +/-   ##
==========================================
+ Coverage   48.14%   48.16%   +0.01%     
==========================================
  Files         109      109              
  Lines       21027    21028       +1     
  Branches     4741     4741              
==========================================
+ Hits        10124    10128       +4     
  Misses       9627     9627              
+ Partials     1276     1273       -3     

Impacted Files	Coverage Δ
tests/unit/ingredients.t	100.00% <ø> (ø)
lib/ProductOpener/Ingredients.pm	90.89% <100.00%> (+0.18%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[benbenben2]

added the slash found in Japanese
fixes #8345

Before

After

[stephanegigandet]

Hi @benbenben2 , the how to learn Perl page is intended to be generic, for Perl newcomers. So it's probably best to not put things that are specific to Product Opener (e.g. where we put logs etc.). The logs are documented here: https://github.com/openfoodfacts/openfoodfacts-server/blob/main/docs/dev/how-to-develop-using-docker.md Maybe the title could be more specific (e.g. How to develop and debug Product Opener using docker) cc @alexgarel

[stephanegigandet]

jp is the country code for Japan, but the language code for Japanese is "ja"

[alexgarel]

Great doc.

But I would have made it a specific how to, and a "how-to-develop-using-perl" that links to how to learn perl, the how to use log, and how-to-write-and-run-tests.md, how-to-use-repl.md and how-to-use-vscode.md

[benbenben2]

thank @alexgarel and @stephanegigandet for the comments regarding the docs. It is rolled back for now. I will spend more time reading the docs and add it in the corresponding page in a future contribution if it is needed.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[stephanegigandet]

Thank you!