-
Notifications
You must be signed in to change notification settings - Fork 15
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
Is it possible to have an option to only show "added" APIs? #21
Comments
I'm having trouble understanding what you're going for. Would you be able to provide an example? |
Right now it shows:
I am looking for:
|
What about changed APIs (which would show up under incompatible changes)? I'm trying to think of a use case where it makes sense to ignore the incompatible changes. Can you explain that part? |
I'm just trying to get them to show up separately so they can be printed into different reports - the request here is for formatting purposes. I'm not trying to "ignore" anything or remove the existing functionality - in my use case I would be calling:
Currently it's nearly impossible to grep out these sections to generate my own reporting and changelogs. For example, I want to show: # APIs removed
golang.org/x/exp/apidiff
Incompatible changes:
- Report.Compatible: removed
- Report.Incompatible: removed
# APIs changed
golang.org/x/exp/apidiff
Incompatible changes:
- Report.Rename: changed from ... to ...
# APIs added
golang.org/x/exp/apidiff
Compatible changes:
- Change: added
- Report.Changes: added
|
The actual change reports are coming from Perhaps I could look into a parsable JSON output format that would make it a bit easier to generate a changelog section. But even then I think changes and removals would be intermingled. If you really want to separate removals and changes, then you may have to parse the message looking for |
Right now it's possible to show:
Is it possible to only show added apis?
The use case is to print 2 separate sections, one for added and one for removed, instead of mixing them together in one.
The text was updated successfully, but these errors were encountered: