Closed wtrocki closed 6 years ago
@wtrocki I don't have enough oversight to have any input on what the service object should look like but not including internals and standardising on a specific format would seem like a no brainer so +1
Thanks for starting this @wtrocki We have a task in the next sprint to do something similar see https://trello.com/c/SNNkv5pH/41-5-as-a-cli-developer-i-want-to-be-able-to-retrieve-my-sdk-config-in-json-format-so-that-i-can-include-it-in-my-mobile-applicatio
If you are ok with it we can use this as a base to complete part of the requirement to have the format well defined and documented, it will also be documented in mobile-core
@maleck13 It will be good to keep SDK team in the loop so we could point how this may work from mobile perspective. Thanks for taking look
@maleck13 @philbrookes - I think that we had really good conversation here and proposal seems to be in good place for initial version. Is it ok to get your review/approval?
We have conversations here on some additional extensions that will be introduced at later stage. As we agreed It's to early to have them in the proposal.
@maleck13 I addressed all comments by applying your suggestions. Because this proposal is related directly with SDK I have created dedicated folder and moved all proposals from top level to sdk
folder. Hope that is ok.
@philbrookes going to go ahead and merge. Further updates and changes can be appended as they come up
Thank You so much guys for involvement and shaping this together!
Really important topic for the SDK maintenance and versioning. I do not have strong opinions about any of the suggested formats - it's just more important to settle on something that will be structured and make sense from mobile point of view.
Motivation
Hide service specific configuration in metadata. Expose common elements to top level to not mix them with metadata.