active-openid contains a UserInfo object with very opinionated fields. This is an unnecessary constraint that can be removed. The library user should be free to pick any container format they choose (or just plain maps) -- we're only responsible for fetching the raw user-info.
In my opinion, we should remove this altogether and break backwards compatibility. I would, however, also be open to provide a legacy implementation of the UserInfo object and related parsers (the ones implicitly defined in fetch-user-info! and fetch-user-info respectively).
active-openidcontains aUserInfoobject with very opinionated fields. This is an unnecessary constraint that can be removed. The library user should be free to pick any container format they choose (or just plain maps) -- we're only responsible for fetching the raw user-info.In my opinion, we should remove this altogether and break backwards compatibility. I would, however, also be open to provide a legacy implementation of the
UserInfoobject and related parsers (the ones implicitly defined infetch-user-info!andfetch-user-inforespectively).