there are a few additional changes that we can cover really briefly and again
I'm just gonna say this still doesn't cover all the changes in spec so you
probably know that before on the previous version we support GFM or
github flavored markdown in descriptions we changed that to cone mark which is now
becoming an official standard for markdown including github or moving to
that or they have most of it to that so there is that extending JSON schema
support actually it's a huge thing but in short we had a support for any of
one of and knots I also say that we still don't support null as a value
but we did introduce a new construct to say that something is inaudible so you
can still specify that that it can have a null another important thing is
something that super mentioned briefly at the beginning we changed the whole
schemas base path and host and we introduced a new contract called server
now server just encompasses all those things but now you can define multiple
servers and give each one a description and you can actually template those
servers so if for example you want to have multiple servers in different
geographical locations and you can specify that the prefix of the host is
completed and give a set of possible values to that support for trace method
again it's not very commonly used in api's but for those you know you can use
it now and we have this sudden that's
also a change we have decided that to follow more the HP spec and in general
payloads are not supported by operations that are defined by the HTTP spec as
having no defined meaning to payloads okay so it's not that the specs when the
spec says and it has no meaning but it has no defined meaning so things like
delete and gets can no longer be defined with payloads yeah so you know as you
can imagine and understand 3.0 is a really big change from 2.0
in terms of the structure and it's pretty much it's a breaking
change all over right so if you want to convert 2.0 specification to a
3.0 one it will require some work, right, so you can see like we talked the
finishes parameters responses your definition is all moved in other
components and some of them have you in a minute or rename you will need to
replace the schemes in the base path with the server's parameters need to be
restructured because even if you have the simple text or simple
primitives parameters you still need to change your structure just a bit
because the schema is oh it always exists and yeah so let's say if
responses have changed quite a bit security as you can see and the only
thing that mostly didn't change is the schema so if you have schemas from 2.0
you can pretty much take them as is and use them in 3.0 the only gotcha there
is that if you did use the discriminator in 2.0 the structure of that did
change in 3.0 so you would have to
make changes to that but beyond that anything else is just the same