Added PassageClientService class

[rickycpadilla]

What's New?

• Added new PassageClientService class to
  • set custom request headers
  • allow for api base path override for testing/developing against non-production endpoints
• Misc
  • Renamed and moved files
  • Made AuthResult return value "discardable" in auth methods
  • Removed Swift Lint as a SPM dependency so consumers aren't forced to download it
  • Misc cleanup

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have manually tested my code thoroughly
• I have added/updated inline documentation for public facing interfaces if relevant
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing integration and unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Jira Ticket

Please add the Jira ticket number and link.

• Jira Ticket: PSG-4469

[SinaSeylani]

After reviewing both PassageClientService.swift and Passage.swift, I couldn't find an overrideBasePath function. Is this something you plan to add later, or is it not part of the Passage Swift roadmap?

[rickycpadilla]

After reviewing both PassageClientService.swift and Passage.swift, I couldn't find an overrideBasePath function. Is this something you plan to add later, or is it not part of the Passage Swift roadmap?

Good question.

I didn't like that overrideBasePath would show up during autocomplete when a customer is typing passage.. They have no need for this method, and should NOT use it.

BUT we do need a public way to override the base path when developing for Flutter and React Native. So now, to override the base path you just need to add a Passage.plist file with the base path override string.