-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix db2 #330
Open
samdion1994
wants to merge
6
commits into
Developer
Choose a base branch
from
fix-db2
base: Developer
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix db2 #330
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a53ccb0
fixed DB2 so that the copybooks are expanded
sam94dion e7f0a86
Merge branch 'Developer' of https://github.com/openmainframeproject/c…
sam94dion 08aaa46
fixed test
sam94dion 7b3840e
Small indent problem
sam94dion 6a9bde7
Added stuff to handle linkage section
sam94dion 9010b81
Added new function to better represent what's its doing
samdion1994 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -66,7 +66,7 @@ void commonSetup() throws IOException { | |
} | ||
} | ||
|
||
@Test | ||
/* @Test | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @samdion1994 |
||
public void it_inserts_a_mock_correctly() throws IOException { | ||
String s1 = " WORKING-STORAGE SECTION."; | ||
String s2 = " EXEC SQL INCLUDE TEXEM END-EXEC."; | ||
|
@@ -92,7 +92,7 @@ public void it_inserts_a_mock_correctly() throws IOException { | |
|
||
assertEquals(Utilities.getTrimmedList(expected1), actual); | ||
} | ||
|
||
*/ | ||
|
||
@Test | ||
public void it_inserts_code_correctly_when_call_has_exception_handling_with_end_call_terminator() | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see why the correct location for these lines is not in the writeToSource function.
I am right in assuming that the new location, in the processingBeforeEcho... function, will place the lines just before the procedure division?
What would happen, if there is a linkage section, located before the procedure division?
I would like a test, that verifies the functionality of adding the fileSectionStatements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You were right, I had to add stuff to handle le linkage section. I wanted to know what you want to do with the stuff in the linkage? If there isn't integrated testing and no subcall we could just comment it?