@rene I believe SE API did not use to include revision_number if a revision wasn't an edit, but I may not be remembering correctly

I had this comment on my code

but it sounds a bit strange to me for SE to change v2.2 code

→ 1 message moved to ­Trash

@double-beep I haven't use that bit of the API. Given how the team is working on technical debt I wouldn't assume they won't change v2.2 code. They probably made the sure the contract between 2.2 and 2.3 didn't break but subtle changes in behavior can be expected.

subtle??

You don't like that word?

I was relying on the existence of revision_number to determine whether a revision was an edit

and to create the revision link

/revisions/<postId>/<revision_number>

but it sometimes breaks

Is that maybe a redaction? There are some cornercases where things that are actual posthistory events end-up as a revision record. I'm not sure if those are by accident or by design. Maybe open a bug on Stack Apps so we can get more eyes on it.

no, definitely not a redaction

What is the endpoint that you expect to return a revison_number?

/posts/{ids}/revisions

what is the revision_type of the post that doesn't return you a revision_number

and the revision_guid?

there's no specific post, you can try with one that has a notice

@double-beep I have a similar thing as well, in an app where I select a revision to rollback to in case of vandalism.

thanks rene for refreshing my memory

yw