Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix missing types and jsDocs #89
fix missing types and jsDocs #89
Changes from 5 commits
42a9693
cbe6e8f
a9e6fa0
7f94d00
f4366dd
977605c
4262c6d
002ae75
babf333
7dc97d7
aad7d48
d242a94
6b3b940
c072f28
9cf82f2
b78e19e
0771cf9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
Check failure on line 1 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 1 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 1 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 1 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you use the suggestion above, I would also declare the
Translations
type like this:I haven't checked, though if
Translations
could be typed separately, rather than looking it up with key access onGetTextTranslations
, that would be preferred. If that is acceptable then it would change to:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes be patient but that is the fastest way with my IDE to generate jsdocs types. a 'cleaner' commit will follow all these changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i just give a try and seems that jsDocs only supports inline import :/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks to me like you didn't import them. Is it okay for me to PR this branch so you can see what I mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure! I think you have even permission to edit my repo, if not tell me
Check failure on line 54 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 54 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 54 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 54 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest
Check failure on line 64 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 64 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 64 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 64 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That assignment appears to have been established at some point, presumably intended for modification through options. However, with no implementation efforts undertaken, it remains as unused memory.
https://nodejs.org/api/buffer.html#bufwriteuint32levalue-offset
These serve as the 'placeholders' for the associated function name utilized for reading bytes from the po/mo files. Frankly, I'm uncertain whether it's worthwhile to implement the others, as file writing should adhere to a similar approach.
this made typing more complicated, what do you say I leave it or is it OK?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would argue that byte order should be an option of the compiler, so rather than remove the concept of changing the write function we should fix it.
If a mo file is parsed in a specific byte order it should be rewritten in the same order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this requires a separate issue. won't fix in this pr
Check failure on line 123 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 123 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 123 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 123 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest
Check failure on line 237 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 237 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 237 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 237 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest
Check failure on line 246 in src/mocompiler.js
GitHub Actions / Node.js 18 on ubuntu-latest
Check failure on line 246 in src/mocompiler.js
GitHub Actions / Node.js 18 on windows-latest
Check failure on line 246 in src/mocompiler.js
GitHub Actions / Node.js 20 on ubuntu-latest
Check failure on line 246 in src/mocompiler.js
GitHub Actions / Node.js 20 on windows-latest