You've already forked joplin
							
							
				mirror of
				https://github.com/laurent22/joplin.git
				synced 2025-10-31 00:07:48 +02:00 
			
		
		
		
	Chore: Implement cSpell to detect spelling mistakes in codebase (#10001)
Co-authored-by: Helmut K. C. Tessarek <tessarek@evermeet.cx> Co-authored-by: Henry Heino <46334387+personalizedrefrigerator@users.noreply.github.com>
This commit is contained in:
		| @@ -18,7 +18,7 @@ export default function useOnMessage( | ||||
| 	noteBody: string, | ||||
| 	callbacks: MessageCallbacks, | ||||
| ) { | ||||
| 	// Dectructure callbacks. Because we have that ({ a: 1 }) !== ({ a: 1 }), | ||||
| 	// Destructure callbacks. Because we have that ({ a: 1 }) !== ({ a: 1 }), | ||||
| 	// we can expect the `callbacks` variable from the last time useOnMessage was called to | ||||
| 	// not equal the current` callbacks` variable, even if the callbacks themselves are the | ||||
| 	// same. | ||||
|   | ||||
| @@ -75,7 +75,7 @@ export default function useSource( | ||||
| 	// If a checkbox in a note is ticked, the body changes, which normally would | ||||
| 	// trigger a re-render of this component, which has the unfortunate side | ||||
| 	// effect of making the view scroll back to the top. This re-rendering | ||||
| 	// however is uncessary since the component is already visually updated via | ||||
| 	// however is unnecessary since the component is already visually updated via | ||||
| 	// JS. So here, if the note has not changed, we prevent the component from | ||||
| 	// updating. This fixes the above issue. A drawback of this is if the note | ||||
| 	// is updated via sync, this change will not be displayed immediately. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user