Either way, this is a nice-to-have, so it's not 100% necessary - just wanted to get the idea out there and looked at just in case a contributor comes along and wants to contribute. Happy to help when I have the time though!

Is your feature request related to a problem? Please describe.

When I'm testing the auth flow locally with the custom IdP I'm developing, I'd like for the token clien

As we attempt to pick up the release cadence, we are in need of an explicit changelog file which enumerates changes in each version. This should be a markdown or plaintext file adhering to some form of standardized format. Ideally, it will be able to work with #582.

We currently use a macro for writing down a money amount as a literal. We should move to a more modern C++ representation with a user defined literal like the below:

constexpr money32 operator"" _GBP(long double money)
{
    return money * 10;
}

static_assert(MONEY(2, 40) == 2.40_GBP);

Go through the codebase and replace all MONEY macro uses with the equivalent version. You m

Context and Description

The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.

If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)

Thanks!

Context
Stuff like the server host name and port are not intuitive to find at all. Right now I find it easier to open the Connect menu and click Edit on the server to get the information, while the actual Information menu should show this a lot clearer.

Describe the feature you have in mind
Improve the readability of the Information menu/dialog. Show information important to the user