> I created a RFC for a plugin called foreman_api_v3 > <https://github.com/isratrade/rfcs/blob/master/0000-foreman-api-v3.md> and > the initial repo at github.com/isratrade/foreman_api_v3. If the community > accepts, I am happy to move this repo to theforeman/foreman_api_v3
Joseph, can you describe in more detail what the change is all about? >From reading the README I can't tell what is going on. This is a great candidate for RFC by the way. > For some background, the Foreman API v2 is more than 3 years old. When I > implemented v2, I used conventions that I thought were good at the time. > The katello had some slightly different conventions, and we weren't always > in sync. This created some challenges for Satellite6 as a single RH > product. > > The goal of JSON API is to create a standardization that is *Flexible, > Consistent, and Fast *-- we can all agree with these goals. > > Here's some more links that could be helpful in addition to > http://jsonapi.org/ > > http://blog.arkency.com/2016/02/how-and-why-should-you-use-json-api-in-your-rails-api/ > > *JSON API <http://jsonapi.org/> is a great solution to not waste hours on > reinventing the wheel in terms of your API responses design.* It is a > great, extensible response standard which can save your time - both on the > backend side and the client side. Your clients can leverage you’re using an > established standard to implement an integration with your API in a cleaner > and faster way. This should go into the RFC really ^^^ -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
