9 Commits (ae0d4189e1f88e657183d3a245d2b5707a91d2bd)

Author	SHA1	Message	Date
Krishan	2301430e37	fix match bracket matching (#10777)	7 months ago
Pascal Kuthe	5b8b2f4b9b	improve match bracket matching (#10613)	7 months ago
Krishan	89a9f2be78	specify direction for select_prev_sibling and select_next_sibling (#10542) ... * specify direction for select_prev_sibling and select_next_sibling * fix failing integration-test	7 months ago
Skyler Hawthorne	c99c333337	Use new in-crate TreeCursor	8 months ago
Skyler Hawthorne	fa67c5c474	feat(command): select_all_children	8 months ago
Skyler Hawthorne	87c4161732	feat(command): select_all_siblings	8 months ago
Skyler Hawthorne	f5991657f4	Factor out line ending handling in integration tests (#9921) ... Prior to this change, every integration test which wanted its line endings to be handled transparently across platforms, i.e. test with the same input that has its platform's line feed characters, converting the line endings was up to each individual test by calling the `platform_line` helper function. This significantly increases the amount of boilerplate one has to copy between all the tests. However, there are some test cases that need to exert strict control over the exact input text without being manipulated behind the scenes by the test framework. So, with this change, the line feed conversions are factored into the `TestCase` struct. By default, line endings of the input text are converted to the platform's native line feed ending, but one can explicitly specify in their test case when the input text should be left alone and tested as is.	8 months ago
Skyler Hawthorne	15e07d4db8	feat: smart_tab ... Implement `smart_tab`, which optionally makes the tab key run the `move_parent_node_start` command when the cursor has non- whitespace to its left.	1 year ago
Skyler Hawthorne	93acb53812	add node boundary movement	1 year ago