-beta.* suffix, for example, 3.2.0-beta.1. For more information on how to use the beta versions, refer to the README in the GitHub repository.UserManagement.get_authorization_url generated url by @csrbarber in https://github.com/workos/workos-elixir/pull/74Full Changelog: https://github.com/workos/workos-elixir/compare/v1.1.1...v1.1.2
Full Changelog: https://github.com/workos/workos-elixir/compare/v1.1.0...v1.1.1
Full Changelog: https://github.com/workos/workos-elixir/compare/1.0.0...v1.1.0
This is the first major release of the WorkOS Elixir SDK, it introduces all of the core APIs from WorkOS released until this moment and provides better configuration support for applications.
However, it'll remain as an experimental SDK since we don't have plans to keep it up to date across core product API changes.
For matching clauses like this one:
case WorkOS.Organizations.get_organization(org_id) do
{:ok,
%{
"id" => id,
"name" => name
}}
It might result in a similar "no clause matching" error:
Responses now have their structs that are parsed from the JSON responses. For instance, here's how to perform matching on the result of get_organization with response structs:
{:ok, %WorkOS.Organizations.Organization{id: id}} =
WorkOS.Organizations.get_organization("org_123")
You may also encounter errors regarding Access Behaviour on Structs.
Introducing a new configuration option: :client, by default, this library uses Tesla but it can be replaced according to the WorkOS.Client module behavior.
However, as previously, the only required config options are :api_key and :client_id.
You can also create a client struct separately, and pass it to each method.
client = WorkOS.client(api_key: System.fetch_env!("WORKOS_API_KEY"), client_id: System.fetch_env!("WORKOS_CLIENT_ID"))
WorkOS.Organizations.get_organization(client, "org_123")
Note that if you choose to configure WorkOS in your app config, passing a client struct is always optional.
config :workos, WorkOS.Client,
api_key: "sk_12345",
client_id: "project_12345"
domain option from WorkOS.SSO.get_authorization_url, organization should be used instead.We're introducing new API modules according to our latest features:
WorkOS.OrganizationDomains: https://workos.com/docs/reference/domain-verificationWorkOS.UserManagement: https://workos.com/docs/reference/user-managementWorkOS.Events: https://workos.com/docs/reference/eventscreate_session causing the expires_in to not be passed in properly #35get_profile causing the access_token to not be passed in properly #29This is an initial beta version release.
This includes support for:
connection to get_authorization_url (#1)