chore(deps) Update all non-major dependencies #4
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:
11.10.4
->11.10.5
5.5.4
->5.8.3
5.5.4
->5.8.3
1.8.5
->1.9.0
18.0.21
->18.0.25
18.0.6
->18.0.9
5.39.0
->5.44.0
5.39.0
->5.44.0
2.1.0
->2.2.0
7.4.0
->7.6.0
0.15.10
->0.15.15
3.3.3
->3.4.1
8.25.0
->8.28.0
4.18.1
->4.18.2
8.0.1
->8.0.2
1.2.6
->1.2.7
3.1.0
->3.2.0
2.7.1
->2.8.0
8.0.4
->8.0.5
4.5.2
->4.5.4
4.5.2
->4.5.4
4.8.4
->4.9.3
3.1.6
->3.2.4
8.9.0
->8.11.0
Release Notes
emotion-js/emotion
v11.10.5
Compare Source
Patch Changes
#2929
13afe030
Thanks @Andarist! - The support for@container
queries has been added by updating the underlying parser (stylis) .Updated dependencies [
13afe030
,c02b1214
]:mantinedev/mantine
v5.8.3
Compare Source
What's Changed
[@mantine/dropzone]
AddonDropAny
prop to capture both accepted and rejected files (#3010)[@mantine/tiptap]
Fix incorrect content border-radius[@mantine/tiptap]
Fix placeholder extension not working as expected[@mantine/core]
Drawer: Add missingaria-describedby
andaria-labelledby
attributes to the root element (#3027)[@mantine/core]
NumberInput: Fix value not being formatted correctly when precision changes (#3011)New Contributors
Full Changelog: mantinedev/mantine@5.8.2...5.8.3
v5.8.2
What's Changed
[@mantine/tiptap]
Fix incorrect hr control label[@mantine/tiptap]
Fix incorrecteditor
prop type[@mantine/tiptap]
Fix typo in strikethrough label (#3004)[@mantine/prism]
Fix colorScheme prop not being passed to Prism from Prism.Panel component[@mantine/core]
Pagination: Fix incorrect handling of negative and zero total[@mantine/hooks]
use-pagination: Fix incorrect handling of decimal values passed as total (#2979)[@mantine/core]
NumberInput: Fix readOnly prop not working correctly (#2956)[@mantine/hooks]
Allow usage of use-click-outside and use-focus-trap hooks with shadow DOMNew Contributors
Full Changelog: mantinedev/mantine@5.8.0...5.8.2
v5.8.0
Compare Source
View changelog with demos on mantine.dev website
Tiptap rich text editor
New @mantine/tiptap package is a replacement
for @mantine/rte package.
RichTextEditor
component is now based on Tiptap, it supports all of
Tiptap extensions and provides flexible components API.
@mantine/rte package deprecation
Quill based RichTextEditor is now deprecated.
@mantine/rte
package will no longer receive any updates, support for itwill be discontinued when 6.0.0 version is released. We recommend to switch
to Tiptap based editor as soon as possible.
Other changes
display
style prophexa
formatNew Contributors
Full Changelog: mantinedev/mantine@5.7.2...5.8.0
v5.7.2
Compare Source
What's Changed
[@mantine/core]
RangeSlider: Fix incorrect minRange handling for negative values (#2897)[@mantine/core]
Slider: Fix unexpected step behavior when min is set to odd number (#2855)[@mantine/core]
Prevent focus shifting from the input when clear button is pressed in Select and MultiSelect components[@mantine/core]
TypographyStylesProvider: Add mark styles[@mantine/core]
Image: Do not show placeholder when image is loading to avoid issues with ssr and rapidly changing src prop[@mantine/core]
Slider: Fix incorrect marks styles wheninverted
prop is set (#2894)[@mantine/core]
Fix incorrect label alignment in Checkbox, Radio and Switch components when label is a ReactNode (#2881)[@mantine/core]
Modal: Fix incorrect click outside behavior (#2896)[@mantine/core]
Radio: Fix size prop not being respected when used within Radio.Group (#2913)New Contributors
Full Changelog: mantinedev/mantine@5.7.1...5.7.2
v5.7.1
Compare Source
What's Changed
[@mantine/hooks]
use-window-event: Fix event listener not being updated when event type or function changes[@mantine/spotlight]
Allow overriding autoComplete prop with searchInputProps[@mantine/core]
Menu: Allow overriding Menu.Item button type[@mantine/hooks]
use-scroll-into-view: Fix parameters changes being ignored (#2866)[@mantine/hooks]
use-local-storage: Fix incorrect value returned ifdefaultValue
is not specified (#2872)[@mantine/styles]
Add missingright
style prop (#2887)[@mantine/form]
Add missingTransformValues
type tocreateFormContext
(#2893)New Contributors
Full Changelog: mantinedev/mantine@5.7.0...5.7.1
v5.7.0
Compare Source
View changelog with demos on mantine.dev website
Style props
All Mantine components now support responsive style props:
Flex component
Flex component is an alternative to Group and Stack components.
It supports new responsive style props:
Focus ring styles on theme
You can now customize focus ring styles for all components in MantineProvider:
Responsive Header and Footer height
Header and Footer components now support responsive height:
Other changes
axis
prop, it is now possible to animate widthloaderPosition="center"
onSlideChange
proponSubmit
can now be called without form eventwithKeyboardEvents
prop that allows to disable keyboard events handlingNew Contributors
Full Changelog: mantinedev/mantine@5.6.4...5.7.0
v5.6.4
Compare Source
What's Changed
[@mantine/core]
Slider: Fix incorrect min/max values handling (#2839)[@mantine/core]
ScrollArea: Fix incorrect ref usage in demosNew Contributors
Full Changelog: mantinedev/mantine@5.6.3...5.6.4
v5.6.3
Compare Source
What's Changed
[@mantine/core]
Fix incorrect focus ring styles in Chip, SegmentedControl and ColorPicker components (box-shadow was replaced with outline)[@mantine/core]
Drawer: FixtransitionDuration
not being respected for exit transition (#2820)[@mantine/core]
Pagination: Fixtheme.fontFamily
not being respected (#2796)[@mantine/form]
Fix required transform value type in UseFormInput (#2816)[@mantine/styles]
Setcolor-scheme
style in html element (#2808)[@mantine/core]
Add data-checked attribute to Checkbox, Radio and Switch when components are used within groups[@mantine/styles]
Fix incorrect styles params type in strict ts modeNew Contributors
Full Changelog: mantinedev/mantine@5.6.2...5.6.3
v5.6.2
Compare Source
What's Changed
[@mantine/core]
Modal: Fix modal not being centered because of scrollbars offset[@mantine/core]
MultiSelect: Fix poor selected values contrast with light color scheme and filled input variant[@mantine/dropzone]
Fix Dropzone.FullScreen opened when the user selects and drags text on the page[@mantine/core]
NativeSelect: Fix incorrect defaultValue handing in controlled components[@mantine/rte]
Fixtheme.defaultRadius
not being respected by some controls (#2781)[@mantine/styles]
Improve useComponentDefaultProps types (#2065)[@mantine/core]
AddarrowRadius
support to Tooltip and Popover (#2779)New Contributors
Full Changelog: mantinedev/mantine@5.6.1...5.6.2
v5.6.1
Compare Source
What's Changed
[@mantine/core]
Popover: Set default width to max-content to reduce position shift in some cases (#2500)[@mantine/core]
Popover: Add position fallback to reduce postion shift (#2500)[@mantine/core]
Slider: Fix incorrect min/max boundaries handling when step is larger than the difference between current value and min/max (#2656)[@mantine/hooks]
use-idle: Improve types for events (#2704)[@mantine/hooks]
use-focus-trap: Fix incorrect aria-hidden handling (#2735)[@mantine/core]
Popover: Fix infinite loop when component is used with Preact (#2752)[@mantine/core]
Tooltip: Add nested tooltips support (#2768)[@mantine/core]
TransferList: AddtransferIcon
,transferAllIcon
props, controlled search and tuple syntax forseachPlaceholder
andnothingFound
props (#2769)[@mantine/dropzone]
Update react-dropzone to 14.2.3 to fix OS detection issue (#2746)[@mantine/form]
Fix incorrect required second argument in UseFormReturnType (#2758)[@mantine/core]
Rating: Fix count and fractions parameters to accept integers only (#2763)[@mantine/core]
Rating: Fix broken react 17 compatibilityNew Contributors
Full Changelog: mantinedev/mantine@5.6.0...5.6.1
v5.6.0
Compare Source
View changelog with demos on mantine.dev website
Rating component
New Rating component:
Progress sections props
Progress and RingProgress
components now support adding props to sections:
use-favicon hook
New use-favicon hook:
Form index reference in validateInputOnBlur and validateInputOnChange
You can now use
FORM_INDEX
in use-form to validate nested array fields withvalidateInputOnBlur
andvalidateInputOnChange
settings:use-form transformValues
use-form now supports
transformValues
options, it transforms values before they get submitted inonSubmit
handler.For example, it can be used to merge several fields into one or to convert types:
Other changes
readOnly
disabled
propstyles
prop can now usetheme
placement
propNew Contributors
Full Changelog: mantinedev/mantine@5.5.6...5.6.0
v5.5.6
Compare Source
What's Changed
[@mantine/core]
Tooltip: Add position fallback to reduce position shift (#2500)[@mantine/dates]
Remove obsolette props from Calendar and DatePicker components (#2648, #2714)[@mantine/core]
Image: Fix incorrect placeholder size calculation when width/height is not set (#2675)[@mantine/core]
Popover: Fix issue when dropdown could be scrolled pass its target (#2694)[@mantine/core]
Menu: Fix incorrect logic for controlled opened state (#2701)[@mantine/core]
PasswordInput: Fix inputContainer and iconWidth props not workingNew Contributors
Full Changelog: mantinedev/mantine@5.5.5...5.5.6
v5.5.5
Compare Source
What's Changed
[@mantine/core]
NumberInput: FixremoveTrailingZeros
prop not working for initial value (#2638)[@mantine/core]
Modal: Fix issue when it was impossible to interact with scrollbars behind overlay (#2669)[@mantine/styles]
Fix incorrect params handling in DefaultProps type in strict mode[@mantine/core]
Select: Fix component scrolling page when it is focused without any data or nothing found message (#2628)[@mantine/core]
Fix Avatar and ThemeIcon components not respectingtheme.defaultGradient
(#2649)[@mantine/dates]
Calendar: Fix error in console when up/down error is pressed and next/previous date is disabled[@mantine/core]
Menu: Close menu when target changes (#2646)[@mantine/hooks]
use-focus-return: Add preventScroll: true to avoid scrolling to element when dropdown/modal is closed outside of current viewportNew Contributors
Full Changelog: mantinedev/mantine@5.5.4...5.5.5
reduxjs/redux-toolkit
v1.9.0
Compare Source
This feature release adds several new options for RTK Query's
createApi
andfetchBaseQuery
APIs, adds a newupsertQueryData
util, rewrites RTKQ's internals for improved performance, adds a newautoBatchEnhancer
, deprecates the "object" syntax forcreateReducer
andcreateSlice.extraReducers
, deprecates and removes broken utils for getting running query promises, improves TS inference, exports additional types, and fixes a number of reported issues.We plan to start work on RTK 2.0 in the next few weeks. RTK 2.0 will focus on dropping legacy build compatibility and deprecated APIs, with some potential new features. See the linked discussion thread and give us feedback on ideas!
Deprecations and Removals
Object Argument for
createReducer
andcreateSlice.extraReducers
RTK's
createReducer
API was originally designed to accept a lookup table of action type strings to case reducers, like{ "ADD_TODO" : (state, action) => {} }
. We later added the "builder callback" form to allow more flexibility in adding "matchers" and a default handler, and did the same forcreateSlice.extraReducers
.We intend to remove the "object" form for both
createReducer
andcreateSlice.extraReducers
in RTK 2.0. The builder callback form is effectively the same number of lines of code, and works much better with TypeScript.Starting with this release, RTK will print a one-time runtime warning for both
createReducer
andcreateSlice.extraReducers
if you pass in an object argument.As an example, this:
should be migrated to:
Codemods for Deprecated Object Reducer Syntax
To simplify upgrading codebases, we've published a set of codemods that will automatically transform the deprecated "object" syntax into the equivalent "builder" syntax.
The codemods package is available on NPM as
@reduxjs/rtk-codemods
. It currently contains two codemods:createReducerBuilder
andcreateSliceBuilder
.To run the codemods against your codebase, run
npx @​reduxjs/rtk-codemods <TRANSFORM NAME> path/of/files/ or/some**/*glob.js
.Examples:
We also recommend re-running Prettier on the codebase before committing the changes.
These codemods should work, but we would greatly appreciate testing and feedback on more real-world codebases!
Object reducer codemod before/after examples
Before:After:
getRunningOperationPromises
Deprecation and ReplacementIn
v1.7.0
, we added anapi.util.getRunningOperationPromises()
method for use with SSR scenarios, as well as a singulargetRunningOperationPromise()
method intended for possible use with React Suspense.Unfortunately, in #2477 we realized that both those methods have a fatal flaw - they do not work with multiple stores in SSR.
As of this release, we are immediately marking
getRunningOperationPromises()
as deprecated and discouraging its use before we remove it completely in RTK 2.0! It will now throw both runtime and compile errors in development to enforce moving away from using it. However, we are leaving its existing behavior in production builds to avoid actual breakage.The
getRunningOperationPromise()
util was experimental, and as far as we can tell not actually being used by anyone, so we are removinggetRunningOperationPromise
completely in this release.As replacements, RTKQ now includes four new thunks attached to
api.util
:getRunningQueryThunk(endpointName, queryArgs)
getRunningMutationThunk(endpointName, fixedCacheKeyOrRequestId)
getRunningQueriesThunk()
getRunningMutationsThunk()
Usages would typically change like this:
Changelog
New RTK Query
createApi
OptionscreateApi
endpoints now have several additional options that can be passed in, some of which are intended to work together.merge
OptionRTKQ was built around the assumption that the server is the source of truth, and every refetch replaces the cached data on the client. There are use cases when it would be useful to merge an incoming response into the existing cached data instead, such as pagination or APIs that return varying results over tim
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.