For Parley to be able to connect to the backend api's hosted on our servers, we need to add some extra headers. Setting pre-configured headers using the Map<String, String> headers parameter doesn't work for us, because our headers need to be created dynamically.
This change would allow is to add the custom headers we need.
I considered adding a new ParleyNetwork constructor, but this would require the client to add the OkHttp networking library (or Retrofit) to be abled to compile the project. That's why I've added a function instead.
For Parley to be able to connect to the backend api's hosted on our servers, we need to add some extra headers. Setting pre-configured headers using the
Map<String, String> headers
parameter doesn't work for us, because our headers need to be created dynamically.This change would allow is to add the custom headers we need.
I considered adding a new ParleyNetwork constructor, but this would require the client to add the OkHttp networking library (or Retrofit) to be abled to compile the project. That's why I've added a function instead.
Thanks,
Menno Vogel