useHash using empty string in the first render

[iGoodie]

What package has an issue

@mantine/hooks

Describe the bug

useHash renders with "" in the first render, making it impossible to declare initial state values with it.
Here's an overly simplified version of my case:

  const [hash, setHash] = useHash();

  const [currentTab, setCurrentTab] = useState(isValidTab(hash) ? hash : Tabs.DESCRIPTION);

However, since internally its initial value is set as an effect on the second render, I can't use it as a barebone for a state initializer.

mantine/src/mantine-hooks/src/use-hash/use-hash.ts

Lines 20 to 22 in b10a096

	useEffect(() => {
	setHashValue(window.location.hash);
	}, []);

What version of @mantine/* packages do you have in package.json? (Note that all @mantine/* packages must have the same version in order to work correctly)

6.0.21

If possible, please include a link to a codesandbox with the reproduced problem

No response

Do you know how to fix the issue

Yes

Are you willing to participate in fixing this issue and create a pull request with the fix

Yes

Possible fix

My solution suggestion would be to replace the following line:

mantine/src/mantine-hooks/src/use-hash/use-hash.ts

Line 5 in b10a096

const [hash, setHashValue] = useState<string>('');

with

  const [hash, setHash] = useState(window.location.hash);

[rtivital]

Fixed in 7.2.1. See https://mantine.dev/hooks/use-hash/#initial-state-value

[iGoodie]

Isn't this statement reversed? @rtivital

mantine/src/mantine-hooks/src/use-hash/use-hash.ts

Lines 8 to 11 in 5f2b215

	export function useHash({ getInitialValueInEffect = false }: UseHashOptions = {}) {
	const [hash, setHashValue] = useState<string>(
	getInitialValueInEffect ? window.location.hash || '' : ''
	);

If the option to use useEffect is set, it uses immediately from window. I think it should be the opposite

getInitialValueInEffect ? '' : window.location.hash || '' 

[rtivital]

Thanks for reporting, the issue will be resolved in the next minor release