You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* save some progress: add basic starter code for folding ranges
* save some progress: add function to traverse through coderange and form folding ranges
* save some progress: add parsing of folding ranges
* fix: maybe issue with foldingRanges
* add: generate folding ranges from coderange
* add: plugin request method instance for folding ranges
* ref: alter function and var names
* post review: cleanup crk to frk & fix typo
* fix: find folding ranges function
* format: run formatter and add comments
* fix: return all response results of folding range request
* Revert "format: run formatter and add comments"
This reverts commit e6a2b5c.
* add: removed comments after revert
* fix: formatting
* docs: add folding range to features section and cabal file
* refactor: use destructuring for createFoldingRange function and use characters
* test: add basic unit test for findFoldingRanges function
* test: add tests for children and code kind
* test: add more test cases
* test: add test for createFoldingRange
* test: add integration test for folding ranges
* fix: duplicate start line foldingranges and remove single line
foldingranges
* refactor: duplicate folding range functionality
* fix: formatting in code range plugin
* added more descriptive comments and encorporate code review suggestions
* revert: automatic formatting for selection range test case file
* fix: ignoring children if root fails to provide folding ranges
* remove: redundant match on crkToFrk
* revert: filtering same line foldings and multiple foldings on the same line as it can be handled by clients
* revert: formatting change to selection range test file
* fix: entire file folding because of root node
Co-authored-by: Kobayashi <contact@zelinf.net>
@@ -261,6 +261,7 @@ Change/Update a type signature to match implementation.
261
261
Status: Until GHC 9.4, the implementation is ad-hoc and relies on GHC error messages to create a new signature. Not all GHC error messages are supported.
262
262
263
263
Known Limitations:
264
+
264
265
- Not all GHC error messages are supported
265
266
- Top-level and Function-local bindings with the same names can cause issues, such as incorrect signature changes or no code actions available.
266
267
@@ -337,6 +338,16 @@ support.
337
338
338
339

0 commit comments