Closed boundlesscalm closed 10 months ago
Since this depends on https://github.com/NordicSemiconductor/pc-nrfconnect-shared/pull/860 (as you wrote) I would usually not base this PR on main
but instead on the branch feat/persisted-verbose-logging
of that PR.
Or do you prefer to keep PRs against main
since this is where the code will end up?
For me basing this PR on feat/persisted-verbose-logging
would make reviewing it independent of that other PR a bit easier, but I can achieve the same by looking at the diff manually at https://github.com/NordicSemiconductor/pc-nrfconnect-shared/compare/feat/persisted-verbose-logging...feat/shared-controlled-nrfutil-modules
At the end it doesn't change a lot, as soon as #860 is merged, the situation will be the same:
main
, then the two commits from #860 should just disappear from this PR. feat/persisted-verbose-logging
, then this PR would automatically change to be against main
as soon as #860 is merged.I wasn't aware that the PR would automatically be redirected against main, that makes this so much nicer. I'll re-target this against the verbose logging branch. Thanks!
@datenreisender Thanks for the suggestions! Implemented all of them and merged your branch.
This PR does a few things, all of which are required to allow shared to log the nrfutil module version which are in use.
get
nrfutil
andnrfutil device
were split into separateindex.ts
files