Discuss how to make application work with v2 & v3 cf api

[nwmac]

From @KlapTrap on November 22, 2017 11:13

Initial thoughts

• Work on an api interface model.
• Most of the work should be done in the reducers and effects
• The store structure shouldn't change
  • Provide mapping to keep entity keys constant
  • This should shelter the components from the api changes and let us develop components without worrying about the api versions.

This work may make us able to handle future versions too.

@richard-cox Lets put our thoughts/note here

Copied from original issue: SUSE#1

[nwmac]

From @KlapTrap on November 22, 2017 13:12

Chatted with @richard-cox

More thoughts:

Have a common file that components can ask for api version specific information, for example:

• Table headers
• Page Components
• Side nav elements

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[nwmac]

From @richard-cox on November 22, 2017 14:15

Looks like inline-relations-depth has been removed (as expected) but the proposal for their replacement has NOT been added (unexpected) (https://github.com/cloudfoundry/cc-api-v3-style-guide#including-related-resources).
It might be worth considering a general way when normalizing (this might be impossible)/some place to request missing data.