-
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
Update mantine monorepo to v7 (major) #343
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-7-mantine-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
October 8, 2023 13:42
4f17a19
to
d48b437
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
October 20, 2023 07:41
d48b437
to
1fb3d01
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
November 6, 2023 00:23
b88389c
to
3a44282
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
November 25, 2023 18:49
d5a92a0
to
dc2c6b5
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
December 5, 2023 00:38
dc2c6b5
to
795ec6c
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
December 17, 2023 00:02
795ec6c
to
87ef5af
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
December 24, 2023 19:34
87ef5af
to
027e13c
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
January 11, 2024 08:28
32e55ca
to
43d5250
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
January 14, 2024 18:19
43d5250
to
8634003
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
February 4, 2024 22:40
8634003
to
7e4e219
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
February 19, 2024 22:11
7e4e219
to
7dbcf23
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
March 2, 2024 21:31
7dbcf23
to
23f02fa
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
March 13, 2024 22:16
c0e7faf
to
52c7709
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
March 23, 2024 13:40
52c7709
to
b8d3ec0
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
April 26, 2024 17:12
a593330
to
54fdf2b
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
April 28, 2024 18:07
54fdf2b
to
5a9dfc6
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
2 times, most recently
from
May 12, 2024 19:06
6569a51
to
a17a144
Compare
renovate
bot
force-pushed
the
renovate/major-7-mantine-monorepo
branch
from
May 26, 2024 19:09
a17a144
to
60fd9e3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^5.2.5
->^7.0.0
^5.2.5
->^7.0.0
Release Notes
mantinedev/mantine (@mantine/core)
v7.8.0
Compare Source
View changelog with demos on mantine.dev website
Auto convert px to rem in .css files
Start from version
1.14.4
postcss-preset-mantinesupports
autoRem
option that can be used to automatically convert allpx
valuesto
rem
units in.css
files.This option works similar to
rem
function. The following code:Will be transformed to:
Note that
autoRem
converts only CSS properties, values in@media
queries arenot converted automatically – you still need to use
em
function to convert them.autoRem
option does not convert values in the following cases:calc()
,var()
,clamp()
andurl()
functionscontent
propertyrgb()
,rgba()
,hsl()
,hsla()
colorsIf you want to convert above values to rem units, use
rem
function manually.Uncontrolled form mode
useForm hook now supports uncontrolled mode.
Uncontrolled mode provides a significant performance improvement by reducing
the number of re-renders and the amount of state updates almost to 0. Uncontrolled
mode is now the recommended way to use the
useForm
hook for almost all use cases.Example of uncontrolled form (
form.values
are not updated):form.getValues
With uncontrolled mode, you can not access
form.values
as a state variable,instead, you can use
form.getValues()
method to get current form values at any time:form.getValues()
always returns the latest form values, it is safe to use itafter state updates:
form.watch
form.watch
is an effect function that allows subscribing to changes of aspecific form field. It accepts field path and a callback function that is
called with new value, previous value, touched and dirty field states:
Customize Popover middlewares
You can now customize
middlewares
options in Popover component andin other components (Menu, Select, Combobox, etc.)
based on Popover.
To customize Floating UI middlewares options, pass them as
an object to the
middlewares
prop. For example, to change shiftmiddleware padding to
20px
use the following configuration:use-fetch hook
New use-fetch hook:
use-map hook
New use-map hook:
use-set hook
New use-set hook:
use-debounced-callback hook
New use-debounced-callback hook:
use-throttled-state hook
New use-throttled-state hook:
use-throttled-value hook
New use-throttled-value hook:
use-throttled-callback hook
New use-throttled-callback hook:
use-orientation hook
New use-orientation hook:
use-is-first-render hook
New use-is-first-render hook:
Documentation updates
Other changes
withKeyboardEvents={false}
to disable up/down arrow keys handlingv7.7.2
Compare Source
What's Changed
[@mantine/core]
CloseButton: Add missing disabled styles (#6044)[@mantine/core]
AppShell: Fix incorrect app safe area handling by AppShell.Footer (#6060)[@mantine/core]
NumberInput: Fix cursor position changing when the value is incremented/decremented (#6004)[@mantine/core]
TagsInput: Fix incorrect IME keyboard input handling forBackspace
key (#6011)[@mantine/charts]
Fix incorrect overflow styles of svg element (#6040)[@mantine/core]
PinInput: AddrootRef
prop support (#6032)[@mantine/core]
ScrollArea: FixviewportProps.onScroll
not working (#6055)[@mantine/core]
ScrollArea: Fix incorrect inset position of the horizontal scrollbar (#6059)[@mantine/hooks]
use-local-storage: Fix infinite rerendering with object values (#6022)New Contributors
Full Changelog: mantinedev/mantine@7.7.1...7.7.2
v7.7.1
Compare Source
What's Changed
[@mantine/tiptap]
Improve toolbar items alignment for non-native elements (#5993)[@mantine/spotlight]
Fix incorrect down key handling when the spotlight is opened repeatedly (#5995)[@mantine/core]
Image: Fix ref not being assigned for fallback images (#5989)[@mantine/core]
PinInput: Fix incorrect focus logic (#5963)[@mantine/core]
Table: FixhighlightOnHoverColor
prop not working[@mantine/core]
AppShell: Adjust footer position to include env(safe-area-inset-bottom) (#5502)[@mantine/core]
PinInput: Fix placeholder not being visible on the element that had focus when the component becomes disabled (#5831)[@mantine/dates]
Calendar: Fix double timezone shift (#5916)[@mantine/hooks]
use-local-storage: Fix value not being updated when key is changed (#5910)[@mantine/charts]
Fix incorrect charts legends height for multiline values (#5923)[@mantine/core]
NumberInput: Fix incorrect increment/decrement functions logic whenstep
is a float value (#5926)[@mantine/core]
Combobox: Fix incorrect IME input handling (#5935)[@mantine/core]
Menu: Fix unexpected focus styles in the dropdown element in Firefox (#5957)[@mantine/core]
Fix incorrectdisabled
prop handling in TagsInput and MultiSelect (#5959)[@mantine/core]
FixrenderOption
not working for grouped items in Combobox-based components (#5952)[@mantine/core]
AppShell: Fix error when used inside Suspense (#5979)[@mantine/core]
Update CSS selectors hashing algorithm to prevent collisions with other libraries (#5968)[@mantine/carousel]
Fix specificity issues of some selectors (#5973)[@mantine/core]
AppShell: Fix missing Aside offset in Header and Footer forlayout=alt
(#5974)New Contributors
Full Changelog: mantinedev/mantine@7.7.0...7.7.1
v7.7.0
Compare Source
View changelog with demos on mantine.dev website
Virtual colors
Virtual color is a special color which values should be different for light and dark color schemes.
To define a virtual color, use
virtualColor
function which accepts an object with the followingproperties as a single argument:
name
– color name, must be the same as the key intheme.colors
objectlight
– a key oftheme.colors
object for light color schemedark
– a key oftheme.colors
object for dark color schemeTo see the demo in action, switch between light and dark color schemes (
Ctrl + J
):FloatingIndicator component
New FloatingIndicator component:
ScatterChart component
New ScatterChart component:
colorsTuple function
New
colorsTuple
function can be used to:use-mutation-observer hook
New useMutationObserver hook:
use-state-history hook
New useStateHistory hook:
Axis labels
AreaChart, BarChart and LineChart
components now support
xAxisLabel
andyAxisLabel
props:Documentation updates
mantine-hidden-from-{x}
andmantine-visible-from-{x}
classes.window.HTMLElement.prototype.scrollIntoView
Help center updates
New articles added to the help center:
Other changes
transform: scale()
.connectNulls
andareaProps
propsscrollAreaProps
prop to pass props down to the ScrollArea component in the dropdownfade-up
,fade-down
,fade-left
,fade-right
fade-down
. This change resolves issues with SegmentedControl indicator positioning when used inside modals.fz
andlh
style props withh1
,h2
,h3
,h4
,h5
,h6
valuesv7.6.2
Compare Source
What's Changed
[@mantine/hooks]
use-resize-observer: Fix types (#5847)[@mantine/hooks]
use-local-storage: Fixundefined
being written to the local storage whendefaultValue
is not defined (#5848)[@mantine/core]
NumberInput: FixonValueChange
not being called in increment/decrement functions (#5856)[@mantine/core]
InputWrapper: FixclassName
specified inlabelProps
,descriptionProps
anderrorProps
not being passed to the corresponding element (#5862)[@mantine/core]
Fix some functions not working correctly with TypeScript 5.4 (#5891)[@mantine/form]
FixonValuesChange
not using updated function (#5901)[@mantine/core]
Popover: Fix incorrect dropdown selectors (#5903)[@mantine/core]
Indicator: Fix processing animation in Safari (#5908)[@mantine/hooks]
use-headroom: Fix incorrect pinning logic when scrolling up (#5793)[@mantine/dropzone]
Add heic images format to default mime types (#5867)[@mantine/core]
Transition: Fix transitions resolving instantly in some cases (#5873)[@mantine/dropzone]
AddinputProps
prop support to pass props down to the underlying hidden input element (#5880)[@mantine/core]
Timeline: FixautoContrast
being passed to the dom node as attribute (#5890)New Contributors
Full Changelog: mantinedev/mantine@7.6.1...7.6.2
v7.6.1
Compare Source
What's Changed
[@mantine/core]
Fix incorrect focus ring styles in Button.Group and ActionIcon.Group components (#5736)[@mantine/core]
Progress: Fix incorrect border-radius with multiple sections[@mantine/dates]
DateTimePicker: FixminDate
andmaxDate
not being respected in time input (#5819)[@mantine/core]
Switch: Userole="switch"
for better accessibility (#5746)[@mantine/hooks]
use-resize-observer: Fix incorrect ref type (#5780)[@mantine/dates]
FixpopoverProps.onClose
overriding original component value in DatePickerInput and other similar components (#4105)[@mantine/core]
Fix incorrect Escape key handling in Modal and Drawer components in some cases (#2827)[@mantine/core]
Combobox: Fix incorrect Escape key handling in Modal, Drawer and Popover[@mantine/core]
Transition: Fix transition resolving instantly in some cases (#3126, #5193)[@mantine/core]
Remove loader from the DOM ifloading
prop is not set on ActionIcon and Button components (#5795)[@mantine/hooks]
use-local-storage: Fix inconsistent default value persistence ifgetInitialValueInEffect
is set (#5796)[@mantine/core]
Select: FixautoComplete
prop not working (#5813)[@mantine/core]
Tabs: Fix incorrect border styles in outline variant[@mantine/core]
Checkbox: Fix incorrectindeterminate
+disabled
styles for outline variant (#5806)[@mantine/core]
SegmentedControl: Fix indicator state not being updated correctly when controlled state changes to a value that is not present in the data array (#5689)[@mantine/core]
Fix incorrect label offset with left label position in Checkbox, Switch and Radio components (#5823)[@mantine/core]
PinInput: Fix updating controlled value to an empty string working incorrectly[@mantine/core]
Menu: Fix incorrect role of dropdown elementsNew Contributors
Full Changelog: mantinedev/mantine@7.6.0...7.6.1
v7.6.0
: 🌟Compare Source
View changelog with demos on mantine.dev website
Container queries support
You can now use container queries
with Mantine components.
rem
andem
functions from postcss-preset-mantineare available in container queries staring from
postcss-preset-mantine@1.13.0
.RadarChart component
New RadarChart component:
FocusTrap.InitialFocus component
FocusTrap.InitialFocus is a new component that adds a visually hidden
element which will receive the focus when the focus trap is activated.
Once
FocusTrap.InitialFocus
loses focus, it is removed from the tab order.For example, it is useful if you do not want to focus any elements inside the Modal when it is opened:
New MantineProvider props
MantineProvider now includes more props to control how styles
are generated and injected. These props are useful if you use Mantine as a headless library
and in test environments.
deduplicateCssVariables
deduplicateCssVariables
prop determines whether CSS variables should be deduplicated: if CSS variable has the same value as in default theme, it is not added in the runtime.By default, it is set to
true
. If set tofalse
, all Mantine CSS variables will be added in<style />
tageven if they have the same value as in the default theme.
withStaticClasses
withStaticClasses
determines whether components should have static classes, for example,mantine-Button-root
.By default, static classes are enabled, to disable them set
withStaticClasses
tofalse
:withGlobalClasses
withGlobalClasses
determines whether global classes should be added with<style />
tag.Global classes are required for
hiddenFrom
/visibleFrom
andlightHidden
/darkHidden
props to work.By default, global classes are enabled, to disable them set
withGlobalClasses
tofalse
. Note thatdisabling global classes may break styles of some components.
HeadlessMantineProvider
HeadlessMantineProvider
is an alternative to MantineProviderthat should be used when you want to use Mantine as a headless UI library. It removes all
features that are related to Mantine styles:
style
attributeLimitations of
HeadlessMantineProvider
:color
,radius
,size
, etc.) will have no effect.lightHidden
/darkHidden
,visibleFrom
/hiddenFrom
props will not work.mt="xs"
will not work, butmt={5}
will.To use
HeadlessMantineProvider
, follow getting started guide and replaceMantineProvider
withHeadlessMantineProvider
.Note that you do not need to use ColorSchemeScript in your application, it will not have any effect,
you can ignore this part of the guide.
Sparkline trendColors
Sparkline now supports
trendColors
prop to change chart color depending on the trend.The prop accepts an object with
positive
,negative
andneutral
properties:positive
- color for positive trend (first value is less than the last value indata
array)negative
- color for negative trend (first value is greater than the last value indata
array)neutral
- color for neutral trend (first and last values are equal)neutral
is optional, if not provided, the color will be the same aspositive
.RichTextEditor tasks extension
RichTextEditor now supports tasks tiptap extension:
renderOption prop
Select, MultiSelect, TagsInput and Autocomplete
components now support
renderOption
prop that allows to customize option rendering:Styles improvements
All Mantine components have been migrated to logical CSS properties
(as a replacement for rtl styles) and :where pseudo-class
(as a replacement for private CSS variables). These changes
should not impact the usage of Mantine components, but now Mantine CSS files have smaller size. For example,
@mantine/core/styles.css
now has ~ 8% smaller size (192kb -> 177kb).Pass props to inner recharts components
You can now pass props down to recharts Bar, Area and Line components
with
barProps
,areaProps
andlineProps
props on BarChart, AreaChart and LineChart components.All props accepts either an object with props or a function that receives
series data as an argument and returns an object with props.
PieChart percent labels
PieChart now supports
percent
labels:Documentation updates
Help center updates
New articles added to the help center:
Other changes
swap
handlerform.setFieldValue
now supports callback function as an argumentpx
,py
,mx
andmy
style props now use logical CSS propertiespadding-inline
,padding-block
,margin-inline
andmargin-block
instead ofpadding-left
,padding-right
, etc.me
,ms
,ps
,pe
style props to setmargin-inline-end
,margin-inline-start
,padding-inline-start
and `paddinConfiguration
📅 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.