`npm run build` will destroy correct data and add English name to Japanese name
See original GitHub issueAfter #6787 's merge I use npm run build
command to auto format the data, but I noticed the Japanese name isn’t I just merged.
I manually checked and ensure them, then I run npm run build
in a clear and up-to-date environment, here is a video:
(Sorry, old video mistake cut key point, so this is the full screenrecord)
If video can’t been play:
This may destroy any Japanese name in current data, but I don’t know how to do with it.
I run command on this commit: https://github.com/osmlab/name-suggestion-index/commit/b9a71323af8a3fa157a7b0fceb1d347a7b131f22
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
algoliasearch - npm
A fully-featured and blazing-fast JavaScript API client to interact with Algolia API.. Latest version: 4.14.2, last published: a month ago. Start using ...
Read more >Infrastructure as Code, part 2: build Docker images ... - CircleCI
Running the terraform destroy will terminate any running assets that you created in this tutorial. Run this command to destroy the GKE cluster....
Read more >How to fix Error: listen EADDRINUSE while using NodeJS?
For the webbrowsers it is not a problem: I can surf on the internet, while the server is running. The server is: net.createServer(function...
Read more >How to Use Koa to Build Simple Web Apps | by John Au-Yeung
In this article, we will build an address book app. Users can add, edit, and remove contacts and also view them in a...
Read more >Laravel 8 CRUD Tutorial Example Step By Step From Scratch
The name and price are our custom fields that the user can add via the webforms. You can run the migration to create...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok I think code I added in 03b393459 should mean that
npm run build
should not overwrite the local tags anymore… I’m definitely ok with using the bilingual mainname
andbrand
tags if this is what the local communities prefer. 👍I think it is this code from the build script: https://github.com/osmlab/name-suggestion-index/blob/6e93a1c62edb33aea1b378e466711c87f327b4ed/scripts/build_index.js#L501-L503
The intent was to try to set default values for the language and locationset, but I agree that this rule is being too aggressive and it shouldn’t overwrite tags, so I’ll change it…