Closed alexanderwallin closed 6 years ago
Looks nice, could you update Readme with info about this new option? I'm currently on parental leave so I might not have time to do a merge and publish to NPM but maybe Larsson or Storm has the time.
Ah, good on you!
@MickeLarsson Wanna have a look?
It does remind of that in practice, but I think it conveys its function inaccurately. For instance, – in theory – you might --force
a merged pot in the case of issues/warnings/conflicts at the vendor's side.
@MickeLarsson Thanks! Could you publish a new release, please?
No Prob! Another one? I published 3.2.0 containing the changes yesterday - https://www.npmjs.com/package/narp
Ah! Would you just push the version commit then? <3
Oh... forgot that. Pusheded it now.
Sometimes you might want to do a fresh push, for instance when your 1000 strings limit on Poeditor has been reached. 😬
Adding
--fresh
(or passingfresh: true
) to thepush
skips the merge with the current upstream pot and pushes the extract pot contents as is.I made use of async/await, since the conditional merge resulted in a rather ugly
.then()
sauce.