Issue#520: improve scoping for ABL functions that do not always require parentheses#76
Closed
PeterJudgeZA wants to merge 1 commit into
Closed
Issue#520: improve scoping for ABL functions that do not always require parentheses#76PeterJudgeZA wants to merge 1 commit into
PeterJudgeZA wants to merge 1 commit into
Conversation
Collaborator
|
After having merged the other PR, there's a merge conflict with this PR. Can you squash and rebase? |
Collaborator
|
I tried to squash and rebase myself, but then there were unit test failures so it's better that you take care of it. |
Collaborator
|
First commit is not correct. |
Collaborator
|
Merged in main. I removed all new files (mostly called |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
TODAYandGUIDare now appropriately scoped assupport.function.ablFor vscode-abl/vscode-abl#520