* Add README.ja.md for translation
* Translate intro of README into Japanese
* Translate table of contents of README into Japanese
* Translate current status section of README into Japanese
* Translate what-are-declaration-files section of README into Japanese
* Translate testing (with real code) section of README into Japanese
* Translate section about editing/creating packages in README into Japanese
* Translate common mistakes section of README into Japanese
* Translate remove a package section of README into Japanese
* Translate sections about linting and testing of README into Japanese
* Translate Definition Owners section of README into Japanese
* Translate FAQ section of README into Japanese
* Translate License section of README into Japanese
* Fix some typos etc.
* Remove whitespace next to code block in full-width parentheses
* Add link to README.ja.md in README.md
* Add comments to ask translators to add link to README.ja.md in other language versions
* Fix heading anchors
* Fix translation of 'in order of how much they inconvenience users of a library'
* Update some expressions
* Apply suggestions by sasurau4 from code review
Co-authored-by: Daiki Ihara <sasurau4@gmail.com>
Co-authored-by: Daiki Ihara <sasurau4@gmail.com>
* Move tslint.json advice from PULL_REQUEST_TEMPLATE.md
* Apply suggestions from code review
Co-authored-by: Eli Barzilay <eli@barzilay.org>
* Apply suggestions from code review
Co-authored-by: Eli Barzilay <eli@barzilay.org>
* Keep the most important bit in PULL_REQUEST_TEMPLATE.md
Co-authored-by: Eli Barzilay <eli@barzilay.org>
* fix not-needed script regression, introduced by removing of the sourceRepoURL parameter in #49620 (3868b76e67)
* doc fix example of npm run not-needed
Sorry, I tried, but turns out that I was naive -- there's too much stuff to go over, and especially with languages that I can't read I worry about mistakes. More than that, one of the changes I *did* like was how it organizes tables in a readable way, but then I realized that some of the translations had their own text in the tables and I don't even know if it's common (or possible) to use monospace font, so this can end up messier than what it starts with.
So overall, I think that it's best to leave the texts as-is.
I could do that over just the english version, and revert the edits in the other files, and hope that translations will eventually catch up --- but that would leave much fewer changes, so it might be pointless.
* Add `npm test` instructions to README
* Rename test tasks
lint -> test
test -> test-all
lint is still around for backward compatibility
* add missed close quote
* Adds Brazilian Portuguese README
Co-Authored-By: Pedro Campos <pedro@cdias.dev>
* Fixes some typos
* Changes End of Line Sequence to LF
* Translates anchors
Co-authored-by: Pedro Campos <pedro@cdias.dev>
* Improve docs on 'testing' a dt module
* Duplicate saying how you can test your tests
* Apply suggestions from code review
Co-Authored-By: Nathan Shively-Sanders <293473+sandersn@users.noreply.github.com>
* Update docs with recommendations
* Apply suggestions from code review
Co-Authored-By: Nathan Shively-Sanders <293473+sandersn@users.noreply.github.com>
* Changes from reviews and link from the PR template
Co-authored-by: Nathan Shively-Sanders <293473+sandersn@users.noreply.github.com>
1. Only index.d.ts is allowed in files list; all other d.ts files should be
referenced from it.
2. Unreferenced files that nonetheless need to ship can be added to
OTHER_FILES.txt
