-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Update ZAP Go Package, Fix Generation Issues, and Autogenerate Interface #21
base: master
Are you sure you want to change the base?
Changes from all commits
023c2f2
6890df6
af7152a
4cf6a11
7214bd2
33032b7
79f4a71
5425811
cc0d765
bcfe2b6
00781ca
8b3b5a0
20074b0
32a8927
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,3 +22,6 @@ _testmain.go | |
*.exe | ||
*.test | ||
*.prof | ||
|
||
zaproxy/ | ||
zap-extensions/ | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
module github.com/zaproxy/zap-api-go | ||
|
||
go 1.17 | ||
go 1.22 |
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. This seems wrong, why are they prefixed with 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. There might have been some changes in the generation script. I followed the instructions in the README and executed the commands using Gradle. 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. In that case the instructions were not followed correctly. |
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.
These should be removed, the repos should live at the same level as the
zap-api-go
not under it.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.
What if we link these two projects as submodules instead? This way, users won't need to clone them manually into the correct location. I added them to the .
gitignore
file to ensure they are not committed accidentally.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.
The repos are already cloned, per dev guide.