Update dependency @nordicsemiconductor/pc-nrfconnect-shared to v151 - autoclosed #25
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.
This PR contains the following updates:
147.0.0
->151.0.0
Release Notes
NordicSemiconductor/pc-nrfconnect-shared (@nordicsemiconductor/pc-nrfconnect-shared)
v151.0.0
Changed
usageData
totelemetry
and typeUsageDataMetadata
toTelemetryMetadata
.telemetry
object:enable()
→setUsersAgreedToTelemetry(true)
disable()
→setUsersAgreedToTelemetry(false)
reset()
→setUsersWithdrewTelemetryAgreement()
isEnabled()
→getIsSendingTelemetry()
(which now does not loganymore)
sendUsageData()
→sendEvent()
ErrorBoundary
the propertysendUsageData
is renamed tosendTelemetryEvent
.Steps to upgrade when using this package
usageData
andUsageDataMetadata
as well as the renamed functions mentioned above.
ErrorBoundary
, rename the propertysendUsageData
tosendTelemetryEvent
.v150.0.0
Removed
Overlay
tooltip inner padding should be set by the content within it.Added
shutdown. Otherwise when at that time someone still tries to send IPC
messages to the launcher window, an exception is thrown.
Fixed
Overlay
tooltips weren't centered due to incorrect sizing styles.exception in the main process got thrown. The “certain ways” make this a bit
hard to reproduce: On macOS this happened, when the nrfutil executable did
not have the executable file mode. Usually this should not happen, because
we set that mode ourselves correctly.
v149.0.0
Added
openFile
export.Changed
es6
->es2021
in eslint configenv
.Fixed
isVerboseLogging
persistent setting get/set compatible with Mainthread code (by using
globalThis
instead ofwindow
).v148.0.0
Added
getModule
export from@nordicsemiconductor/pc-nrfconnect-shared/nrfutil
to retrieve/initialise specific nrfutil module sandbox.
setVerboseLogging
,setLogLevel
andgetAllModuleVersions
exports from@nordicsemiconductor/pc-nrfconnect-shared/nrfutil
to target allinitialised nrfutil modules.
Changed
isLoggingVerbose
persisted state is now saved in the app specific store.isLoggingVerbose
now reflects the current verbose logging state(previously this was only used to determine whether an app should have
verbose logging enabled on startup). This allows code which does/should not
have access to the redux store to still retrieve the verbose logging state.
Create system report
now logs the version of all initialised nrfutilmodules.
@nordicsemiconductor/pc-nrfconnect-shared/nrfutil/device
.Steps to upgrade
@nordicsemiconductor/pc-nrfconnect-shared/nrfutil
to@nordicsemiconductor/pc-nrfconnect-shared/nrfutil/device
.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.