-
Notifications
You must be signed in to change notification settings - Fork 0
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
feature request: add the new keys values down the tree #84
Comments
What if u had: {
"example": {
"key1": "value1"
},
"example2": {
"key2": "value2"
}
} And add new key "example.key3"? And git should always show changes only, no matter where they are |
i see that git example delete everything than add everything |
look even if 1 line is change git delete everything and adds everything |
this make the review hard to get the changes |
There were 2 spaces, but after inio there 1 tab? Do u use prettier or something like that? |
yes
Le jeu. 20 juin 2024, 18:11, Alexander Savelyev ***@***.***>
a écrit :
… There were 2 spaces, but after inio there 1 tab?
Do u use prettier or something like that?
—
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOVF6FR7CXE3U6DYDUXRLPLZIMELXAVCNFSM6AAAAABJUKPZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGE3DMNBYGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
i use prettier |
The problem is that sometimes it format your code, sometimes its not. You can use husky and format it each time on precommit. From my side I will think about inio format style |
so there is some incostincies between inio styles and inio styles |
Between inio formatting and prettier formatting* And it is logical. Inio have no idea about your formatters and linters (and shouln't) |
whar you propose souloution for this |
For now - "You can use husky and format it each time on precommit" [by prettier to keep the same codestyle which declared in prettier rules] But I will think in additional |
Closing this task because the problem is not in this (and this cannot be done for reasons described above). Opened a task on indent style rules - #98 |
you know better PS: the adviece you told me about worked well i mean husky with prettier formating at least reduced 6000 lines to 600 lines |
hope you tackle the search missing value on all project issue or , repititive keys issue |
I keep them in mind, looking for a suitable solution |
at least make a i18n dir like scan by dir
Le dim. 30 juin 2024, 21:01, Alexander Savelyev ***@***.***>
a écrit :
… I keep them in mind, looking for a suitable solution
—
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOVF6FTIOXSUHFQRIJ52WQTZKBPYLAVCNFSM6AAAAABJUKPZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGY4DGOBZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Indent rules shipped. Configure it just like your prettier rules.
module.exports = {
indent: {
size: 1,
type: "tab",
},
}; |
example when i have a json with missing value in certain locale and i use inio to add the missing value
inio adds the missing value + key to the end
reason : when use gitadd and commit only new keys would be shown or added stuff
The text was updated successfully, but these errors were encountered: