Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 05 18:43

    ahx on v0.14.2

    (compare)

  • Oct 05 18:41

    ahx on parse-empty-query-parameter

    (compare)

  • Oct 05 18:41

    ahx on master

    Return 400 if query parameter i… 0.14.2 Merge pull request #122 from ah… (compare)

  • Oct 05 18:41
    ahx closed #122
  • Oct 05 13:28
    ahx synchronize #122
  • Oct 05 13:28

    ahx on parse-empty-query-parameter

    Return 400 if query parameter i… 0.14.2 (compare)

  • Oct 05 13:25
    ahx opened #122
  • Oct 05 13:25

    ahx on parse-empty-query-parameter

    Return 400 if query parameter i… 0.14.2 (compare)

  • Oct 05 10:16

    ahx on v0.14.1

    (compare)

  • Oct 05 10:15

    ahx on master

    0.14.1 (compare)

  • Oct 05 10:13

    ahx on master

    0.14.1 (compare)

  • Oct 05 10:10

    ahx on master

    Use Ruby 3.0.2 in development Don't modify path-level paramet… Merge pull request #121 from ah… (compare)

  • Oct 05 10:10

    ahx on fix-mixed-nested-param

    (compare)

  • Oct 05 10:10
    ahx closed #121
  • Oct 05 10:08
    ahx opened #121
  • Oct 05 10:08

    ahx on fix-mixed-nested-param

    Use Ruby 3.0.2 in development Don't modify path-level paramet… (compare)

  • Oct 05 09:34

    ahx on remove-travis

    (compare)

  • Oct 05 09:34

    ahx on master

    No need to stub constants here Remove travis-ci Using Github … Merge pull request #120 from ah… (compare)

  • Oct 05 09:34
    ahx closed #120
  • Oct 05 09:07
    ahx opened #120
Alex Oliveira
@kurko
Hi
I'm currently writing my docs, later I'll try out this gem. I had added committee originally to research how it worked (and if it worked at all). The problem is that I'm using Stoplight's Studio to generate the YAML file and it's generating with 3.1 syntax (not being familiar with OAS previously, I totally missed it). It didn't work then, as described in interagent/committee#270.
I might have to edit the YAML by hand later for the YAML to be able to work nicely with other tools. Looking at ahx/openapi_first#46 is good news. I might be able to help out with that when I get to the point of implementing the end points (provided my company agrees with contributing my time to it) :pray:
Andreas Haller
@ahx
Hi @kurko, welcome to this channel! This is so cool.
I have had a Problem with using Stoplight Studio and committee when using parameters like name: "filter[something]", but that seems to with openapi_first.
Andreas Haller
@ahx
If you have any hickups while using oasf (openapi_first), please don't hesitate to :bell: me.
Alex Oliveira
@kurko
Sure. Going to do what I can to support the project.
I'll probably get to it 2 weeks from now or later
Andreas Haller
@ahx
To be fair: Commitee has some advantages over oasf like having a ResponseValidator middleware (this will be in the next release), validating headers, being able to customize erorr responses and maybe others. However, I think there is a place for oasf.
…ResponseValidator will be available in the next version of oasf.
Alex Oliveira
@kurko
So, what was the main motivation behind developing your own gem instead of using Committee?
Andreas Haller
@ahx
Comittee did not support OAS 3 properly when I started the project.
And I wanted to have something where you specify your paths (like /api/pets/{pet_id} in your OpenAPI only to implement the API.
… this is done via the OpenapiFirst::Router and OpenapiFirst::Responder. Router looks up the current operation and Responder calls a method that you have to implement to generate the response.
Currently Responder looks up the method by looking at the operationId field in your OAS file. This was inspired by https://github.com/zalando/connexion.
Andreas Haller
@ahx
You can still just use the request validation part of oasf and use sinatra or the like, but the idea of Responder is that you don't need to.
Responder is something that I'd like to change in the future to that you can customize what method is called or make handlers look more like Hanami::Action.
I am also not sure if having all middlewares packed togehter in one "standalone-mode" (https://github.com/ahx/openapi_first#standalone-usage) is something people want.
Andreas Haller
@ahx
Here is a feature comparison between committee and openapi_first https://gist.github.com/ahx/1538c31f0652f459861713b5259e366a
Alex Oliveira
@kurko
Great! The only thing I will need is Support custom error response. I can help with a PR later when I get to that point.