Basic Beta Cortex API + Employer Integration POC

[toastercup]

Purpose:

This PR implements a very rudimentary RESTful API for Beta Cortex's ContentItems and ContentTypes. This is by no means future-proofed and will be scrapped in a couple quarters - but it accomplishes the goal of liberating our data. Lacking are easy ways for the consuming application to query FieldItem data, retrieve related ContentItems<->ContentItems, etc. I've purposefully commented out some lines of code as placeholders - these will be implemented in another PR I plan on pushing this weekend or next (implementing tenancy, some very basic filtering and finding, etc). This PR also implements a POC for the Employer Integration ContentType. This was put together a few weeks back to demonstrate how quickly we can spin up new ContentTypes as needs arise.

JIRA:

N/A

Steps to Take On Prod

N/A - eventually, we'll want to seed the Employer Integration ContentType, but since it's a POC and is not complete, we will hold off on doing so.

Changes:

• Changes to setup

  • N/A

• Architectural changes

  • N/A

• Migrations

  • You must manually seed the new Employer Integration ContentType - it is not yet part of the reseed task, as it is still a POC. You can manually seed via this command: bundle exec rake employer:integration:seed

• Library changes

  • N/A

• Side effects

  • N/A

Screenshots

• Before
  N/A

• After
  N/A

QA Links:

http://web.cortex-1.development.c66.me/

How to Verify These Changes

• Specific pages to visit

  • http://web.cortex-1.development.c66.me/api/v1/content_items
  • http://web.cortex-1.development.c66.me/api/v1/content_items/feed?content_type_name=*name_of_content_type
  • http://web.cortex-1.development.c66.me/api/v1/content_items/feed/*id

• Steps to take

  • Login
  • Create some ContentItems for each ContentType
  • Once authenticated, visit the above URLs, replacing each params as necessary (ID, ContentType name, etc). Ensure API renders data correctly and fully. Ensure pagination works and renders correct headers.
  • Test with each ContentType (employer_blog, employer_integration, media)

• Responsive considerations

  • N/A

Relevant PRs/Dependencies:

This is 1/2 of the PRs (the other will be opened in cortex-client shortly) needed to implement #512

Additional Information

N/A

[arelia]

Creating a media item gives a NoMethodError

[toastercup]

@arelia this seems to be a bug already present in develop - we'll have to get a defect in to address it. Good catch!

[mrfantasticwonders]

I'm noticing the same error as Arelia when creating a media type. Not sure if this was addressed yet beyond the defect that will be created.

[toastercup]

@mrfantasticwonders per my previous comment:

@arelia this seems to be a bug already present in develop - we'll have to get a defect in to address it. Good catch!

[MKwenhua]

Looks good!