Skip to content
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.

paths.changed.{path} does not need the { operations_added, operations_changed, operations_removed } layer #11

Open
gr2m opened this issue Aug 31, 2021 · 2 comments

Comments

@gr2m
Copy link

gr2m commented Aug 31, 2021

Example:

image

E.g. instead of

paths.changed.paths["/app"].operations_changed.get

you could just do

paths.change.paths["/app"].get

The operations_changed is implied by the changed

@gr2m
Copy link
Author

gr2m commented Aug 31, 2021

Oh I think I get it, there might be a case when an operation is removed in a path, in which case we would get

paths.changed.paths["/app"].operations_removed.get

but I don't think that this is currently implemented that way?

@gr2m
Copy link
Author

gr2m commented Aug 31, 2021

I think it would be easier to grasp if you all three of paths.{added,changed,removed} had the same format as paths in the source/target OpenAPI files (paths[path][method]), that way it's clear to see which are the operations that are added, which have been changed, which have been removed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant