These are chat archives for APIs-guru/api-models

24th
Nov 2015
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 00:11
I added some custom sorting for Swagger files. So it have custom sort order for top-level keys and alphabetical for the rest.
What do you think? Maybe some other suggestions?
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 12:18
@IvanGoncharov now in https://cenitsaas.com/directory?spec=swagger only appears the guru-apis, I need improve the design of the page
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 13:13
@sanchojaf Cool :+1:
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 15:53
@bobby-brennan @sanchojaf I want to remove API postfix from title field for example Trello API => Trello
It should make titles better suitable for your need
What do you think?
Bobby Brennan
@bobby-brennan
Nov 24 2015 16:11
Yeah I agree with removing API
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 16:16
@sanchojaf What about you?
Bobby Brennan
@bobby-brennan
Nov 24 2015 16:18
Also "Documentation"
e.g. Pleingo, ODWeather, import.io
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 16:19
and "REST API"
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 21:08
I would like have a general index name for any potencial API that we have interest (with label if we have spec or not ). In that case is possible try to find some specific spec that we don't have. Make sense?
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 21:11
@sanchojaf Not entirely. Do you mean you want API naming schema that is predictable. So you can predict name of API before I add spec. Right?
Or you mean I should have index of all APIs that I know about, even if don't have access to spec?
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 21:34
yes I think that the first case is enough.
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 21:38
Currently I use following algorithm: First level is host field from swagger spec with subdomain stripped(using https://publicsuffix.org/) Second level present if domain has more than one API, so I use service names that in most cases name of sub-domain but sometimes I get it from basePath field. Third level is version field from swagger spec.
So I don't have particular rules for second level :(
If you have idea for some algorithm, I'm open for suggestions.
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 21:44
thanks
that are the raml spec available in mulesoft
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 21:45
Cool thanks
I will check them
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 21:47
3357 apis, but in general they are not good, could be great if you can review.
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 21:49
I will add them in queue, but I have huge list of APIs that I need to process.
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 21:53
thanks you
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 22:00
Do you know this propose the discovery apis format, I think that have many common point with your Json list. maybe is useful
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 22:01
I already support this format
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 22:01
cool
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 22:01
But it has some limitation
It make sense if you use specs in multiply formats
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 22:02
yes is right
Ivan Goncharov
@IvanGoncharov
Nov 24 2015 22:02
but in my case I use only swagger
so it has a lot of duplications
+ Swagger support 'x-' fields
so I think it's simpler to support one format
instead of Swagger + APIs.json
Miguel Sancho Fernandez
@sanchojaf
Nov 24 2015 22:06
ok