From c719c634c3c17b930642aef0d895319baf970c39 Mon Sep 17 00:00:00 2001 From: aeneasr <3372410+aeneasr@users.noreply.github.com> Date: Wed, 15 Jan 2025 10:20:08 +0000 Subject: [PATCH] autogen: regenerate OpenAPI client for v1.16.0 Version: v1.16.0 --- CODE_OF_CONDUCT.md | 145 ------------------- CONTRIBUTING.md | 271 ----------------------------------- SECURITY.md | 56 -------- doc/UiNode.md | 2 +- lib/src/model/ui_node.dart | 31 ++-- lib/src/model/ui_node.g.dart | 7 + pubspec.yaml | 2 +- test/ui_node_test.dart | 2 +- 8 files changed, 27 insertions(+), 489 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md delete mode 100644 CONTRIBUTING.md delete mode 100644 SECURITY.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 9cebaf3..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,145 +0,0 @@ - - - -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible disability, ethnicity, sex characteristics, gender -identity and expression, level of experience, education, socio-economic status, -nationality, personal appearance, race, caste, color, religion, or sexual -identity and orientation. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -- Demonstrating empathy and kindness toward other people -- Being respectful of differing opinions, viewpoints, and experiences -- Giving and gracefully accepting constructive feedback -- Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -- Focusing on what is best not just for us as individuals, but for the overall - community - -Examples of unacceptable behavior include: - -- The use of sexualized language or imagery, and sexual attention or advances of - any kind -- Trolling, insulting or derogatory comments, and personal or political attacks -- Public or private harassment -- Publishing others' private information, such as a physical or email address, - without their explicit permission -- Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Open Source Community Support - -Ory Open source software is collaborative and based on contributions by -developers in the Ory community. There is no obligation from Ory to help with -individual problems. If Ory open source software is used in production in a -for-profit company or enterprise environment, we mandate a paid support contract -where Ory is obligated under their service level agreements (SLAs) to offer a -defined level of availability and responsibility. For more information about -paid support please contact us at sales@ory.sh. - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders have the right and responsibility to remove, edit, or reject -comments, commits, code, wiki edits, issues, and other contributions that are -not aligned to this Code of Conduct, and will communicate reasons for moderation -decisions when appropriate. - -## Scope - -This Code of Conduct applies within all community spaces, and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official e-mail address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the community leaders responsible for enforcement at -[office@ory.sh](mailto:office@ory.sh). All complaints will be reviewed and -investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series of -actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or permanent -ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within the -community. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.1, available at -[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. - -Community Impact Guidelines were inspired by [Mozilla's code of conduct -enforcement ladder][mozilla coc]. - -For answers to common questions about this code of conduct, see the FAQ at -[https://www.contributor-covenant.org/faq][faq]. Translations are available at -[https://www.contributor-covenant.org/translations][translations]. - -[homepage]: https://www.contributor-covenant.org -[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html -[mozilla coc]: https://github.com/mozilla/diversity -[faq]: https://www.contributor-covenant.org/faq -[translations]: https://www.contributor-covenant.org/translations diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index c356300..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,271 +0,0 @@ - - - -# Contribute to Ory client-dart - - - - -- [Introduction](#introduction) -- [FAQ](#faq) -- [How can I contribute?](#how-can-i-contribute) -- [Communication](#communication) -- [Contribute examples](#contribute-examples) -- [Contribute code](#contribute-code) -- [Contribute documentation](#contribute-documentation) -- [Disclosing vulnerabilities](#disclosing-vulnerabilities) -- [Code style](#code-style) - - [Working with forks](#working-with-forks) -- [Conduct](#conduct) - - - -## Introduction - -_Please note_: We take Ory client-dart's security and our users' trust very -seriously. If you believe you have found a security issue in Ory client-dart, -please disclose it by contacting us at security@ory.sh. - -There are many ways in which you can contribute. The goal of this document is to -provide a high-level overview of how you can get involved in Ory. - -As a potential contributor, your changes and ideas are welcome at any hour of -the day or night, on weekdays, weekends, and holidays. Please do not ever -hesitate to ask a question or send a pull request. - -If you are unsure, just ask or submit the issue or pull request anyways. You -won't be yelled at for giving it your best effort. The worst that can happen is -that you'll be politely asked to change something. We appreciate any sort of -contributions and don't want a wall of rules to get in the way of that. - -That said, if you want to ensure that a pull request is likely to be merged, -talk to us! You can find out our thoughts and ensure that your contribution -won't clash with Ory -client-dart's direction. A great way to -do this is via -[Ory client-dart Discussions](https://github.com/orgs/ory/discussions) -or the [Ory Chat](https://www.ory.sh/chat). - -## FAQ - -- I am new to the community. Where can I find the - [Ory Community Code of Conduct?](https://github.com/ory/client-dart/blob/master/CODE_OF_CONDUCT.md) - -- I have a question. Where can I get - [answers to questions regarding Ory client-dart?](#communication) - -- I would like to contribute but I am not sure how. Are there - [easy ways to contribute?](#how-can-i-contribute) - [Or good first issues?](https://github.com/search?l=&o=desc&q=label%3A%22help+wanted%22+label%3A%22good+first+issue%22+is%3Aopen+user%3Aory+user%3Aory-corp&s=updated&type=Issues) - -- I want to talk to other Ory client-dart users. - [How can I become a part of the community?](#communication) - -- I would like to know what I am agreeing to when I contribute to Ory - client-dart. - Does Ory have - [a Contributors License Agreement?](https://cla-assistant.io/ory/client-dart) - -- I would like updates about new versions of Ory client-dart. - [How are new releases announced?](https://www.ory.sh/l/sign-up-newsletter) - -## How can I contribute? - -If you want to start to contribute code right away, take a look at the -[list of good first issues](https://github.com/ory/client-dart/labels/good%20first%20issue). - -There are many other ways you can contribute. Here are a few things you can do -to help out: - -- **Give us a star.** It may not seem like much, but it really makes a - difference. This is something that everyone can do to help out Ory client-dart. - Github stars help the project gain visibility and stand out. - -- **Join the community.** Sometimes helping people can be as easy as listening - to their problems and offering a different perspective. Join our Slack, have a - look at discussions in the forum and take part in community events. More info - on this in [Communication](#communication). - -- **Answer discussions.** At all times, there are several unanswered discussions - on GitHub. You can see an - [overview here](https://github.com/discussions?discussions_q=is%3Aunanswered+org%3Aory+sort%3Aupdated-desc). - If you think you know an answer or can provide some information that might - help, please share it! Bonus: You get GitHub achievements for answered - discussions. - -- **Help with open issues.** We have a lot of open issues for Ory client-dart and - some of them may lack necessary information, some are duplicates of older - issues. You can help out by guiding people through the process of filling out - the issue template, asking for clarifying information or pointing them to - existing issues that match their description of the problem. - -- **Review documentation changes.** Most documentation just needs a review for - proper spelling and grammar. If you think a document can be improved in any - way, feel free to hit the `edit` button at the top of the page. More info on - contributing to the documentation [here](#contribute-documentation). - -- **Help with tests.** Pull requests may lack proper tests or test plans. These - are needed for the change to be implemented safely. - -## Communication - -We use [Slack](https://www.ory.sh/chat). You are welcome to drop in and ask -questions, discuss bugs and feature requests, talk to other users of Ory, etc. - -Check out [Ory client-dart Discussions](https://github.com/orgs/ory/discussions). This is a great place for -in-depth discussions and lots of code examples, logs and similar data. - -You can also join our community calls if you want to speak to the Ory team -directly or ask some questions. You can find more info and participate in -[Slack](https://www.ory.sh/chat) in the #community-call channel. - -If you want to receive regular notifications about updates to Ory client-dart, -consider joining the mailing list. We will _only_ send you vital information on -the projects that you are interested in. - -Also, [follow us on Twitter](https://twitter.com/orycorp). - -## Contribute examples - -One of the most impactful ways to contribute is by adding examples. You can find -an overview of examples using Ory services on the -[documentation examples page](https://www.ory.sh/docs/examples). Source code for -examples can be found in most cases in the -[ory/examples](https://github.com/ory/examples) repository. - -_If you would like to contribute a new example, we would love to hear from you!_ - -Please [open an issue](https://github.com/ory/examples/issues/new/choose) to -describe your example before you start working on it. We would love to provide -guidance to make for a pleasant contribution experience. Go through this -checklist to contribute an example: - -1. Create a GitHub issue proposing a new example and make sure it's different - from an existing one. -1. Fork the repo and create a feature branch off of `master` so that changes do - not get mixed up. -1. Add a descriptive prefix to commits. This ensures a uniform commit history - and helps structure the changelog. Please refer to this - [Convential Commits configuration](https://github.com/ory/client-dart/blob/master/.github/workflows/conventional_commits.yml) - for the list of accepted prefixes. You can read more about the Conventional - Commit specification - [at their site](https://www.conventionalcommits.org/en/v1.0.0/). -1. Create a `README.md` that explains how to use the example. (Use - [the README template](https://github.com/ory/examples/blob/master/_common/README.md)). -1. Open a pull request and maintainers will review and merge your example. - -## Contribute code - -Unless you are fixing a known bug, we **strongly** recommend discussing it with -the core team via a GitHub issue or [in our chat](https://www.ory.sh/chat) -before getting started to ensure your work is consistent with Ory client-dart's -roadmap and architecture. - -All contributions are made via pull requests. To make a pull request, you will -need a GitHub account; if you are unclear on this process, see GitHub's -documentation on [forking](https://help.github.com/articles/fork-a-repo) and -[pull requests](https://help.github.com/articles/using-pull-requests). Pull -requests should be targeted at the `master` branch. Before creating a pull -request, go through this checklist: - -1. Create a feature branch off of `master` so that changes do not get mixed up. -1. [Rebase](http://git-scm.com/book/en/Git-Branching-Rebasing) your local - changes against the `master` branch. -1. Run the full project test suite with the `go test -tags sqlite ./...` (or - equivalent) command and confirm that it passes. -1. Run `make format` -1. Add a descriptive prefix to commits. This ensures a uniform commit history - and helps structure the changelog. Please refer to this - [Convential Commits configuration](https://github.com/ory/client-dart/blob/master/.github/workflows/conventional_commits.yml) - for the list of accepted prefixes. You can read more about the Conventional - Commit specification - [at their site](https://www.conventionalcommits.org/en/v1.0.0/). - -If a pull request is not ready to be reviewed yet -[it should be marked as a "Draft"](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request). - -Before your contributions can be reviewed you need to sign our -[Contributor License Agreement](https://cla-assistant.io/ory/client-dart). - -This agreement defines the terms under which your code is contributed to Ory. -More specifically it declares that you have the right to, and actually do, grant -us the rights to use your contribution. You can see the Apache 2.0 license under -which our projects are published -[here](https://github.com/ory/meta/blob/master/LICENSE). - -When pull requests fail the automated testing stages (for example unit or E2E -tests), authors are expected to update their pull requests to address the -failures until the tests pass. - -Pull requests eligible for review - -1. follow the repository's code formatting conventions; -2. include tests that prove that the change works as intended and does not add - regressions; -3. document the changes in the code and/or the project's documentation; -4. pass the CI pipeline; -5. have signed our - [Contributor License Agreement](https://cla-assistant.io/ory/client-dart); -6. include a proper git commit message following the - [Conventional Commit Specification](https://www.conventionalcommits.org/en/v1.0.0/). - -If all of these items are checked, the pull request is ready to be reviewed and -you should change the status to "Ready for review" and -[request review from a maintainer](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review). - -Reviewers will approve the pull request once they are satisfied with the patch. - -## Contribute documentation - -Please provide documentation when changing, removing, or adding features. All -Ory Documentation resides in the -[Ory documentation repository](https://github.com/ory/docs/). For further -instructions please head over to the Ory Documentation -[README.md](https://github.com/ory/docs/blob/master/README.md). - -## Disclosing vulnerabilities - -Please disclose vulnerabilities exclusively to -[security@ory.sh](mailto:security@ory.sh). Do not use GitHub issues. - -## Code style - -Please run `make format` to format all source code following the Ory standard. - -### Working with forks - -```bash -# First you clone the original repository -git clone git@github.com:ory/ory/client-dart.git - -# Next you add a git remote that is your fork: -git remote add fork git@github.com:/ory/client-dart.git - -# Next you fetch the latest changes from origin for master: -git fetch origin -git checkout master -git pull --rebase - -# Next you create a new feature branch off of master: -git checkout my-feature-branch - -# Now you do your work and commit your changes: -git add -A -git commit -a -m "fix: this is the subject line" -m "This is the body line. Closes #123" - -# And the last step is pushing this to your fork -git push -u fork my-feature-branch -``` - -Now go to the project's GitHub Pull Request page and click "New pull request" - -## Conduct - -Whether you are a regular contributor or a newcomer, we care about making this -community a safe place for you and we've got your back. - -[Ory Community Code of Conduct](https://github.com/ory/client-dart/blob/master/CODE_OF_CONDUCT.md) - -We welcome discussion about creating a welcoming, safe, and productive -environment for the community. If you have any questions, feedback, or concerns -[please let us know](https://www.ory.sh/chat). diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 6104514..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,56 +0,0 @@ - - - -# Ory Security Policy - -This policy outlines Ory's security commitments and practices for users across -different licensing and deployment models. - -To learn more about Ory's security service level agreements (SLAs) and -processes, please [contact us](https://www.ory.sh/contact/). - -## Ory Network Users - -- **Security SLA:** Ory addresses vulnerabilities in the Ory Network according - to the following guidelines: - - Critical: Typically addressed within 14 days. - - High: Typically addressed within 30 days. - - Medium: Typically addressed within 90 days. - - Low: Typically addressed within 180 days. - - Informational: Addressed as necessary. - These timelines are targets and may vary based on specific circumstances. -- **Release Schedule:** Updates are deployed to the Ory Network as - vulnerabilities are resolved. -- **Version Support:** The Ory Network always runs the latest version, ensuring - up-to-date security fixes. - -## Ory Enterprise License Customers - -- **Security SLA:** Ory addresses vulnerabilities based on their severity: - - Critical: Typically addressed within 14 days. - - High: Typically addressed within 30 days. - - Medium: Typically addressed within 90 days. - - Low: Typically addressed within 180 days. - - Informational: Addressed as necessary. - These timelines are targets and may vary based on specific circumstances. -- **Release Schedule:** Updates are made available as vulnerabilities are - resolved. Ory works closely with enterprise customers to ensure timely updates - that align with their operational needs. -- **Version Support:** Ory may provide security support for multiple versions, - depending on the terms of the enterprise agreement. - -## Apache 2.0 License Users - -- **Security SLA:** Ory does not provide a formal SLA for security issues under - the Apache 2.0 License. -- **Release Schedule:** Releases prioritize new functionality and include fixes - for known security vulnerabilities at the time of release. While major - releases typically occur one to two times per year, Ory does not guarantee a - fixed release schedule. -- **Version Support:** Security patches are only provided for the latest release - version. - -## Reporting a Vulnerability - -For details on how to report security vulnerabilities, visit our -[security policy documentation](https://www.ory.sh/docs/ecosystem/security). diff --git a/doc/UiNode.md b/doc/UiNode.md index c5cd72f..11ae714 100644 --- a/doc/UiNode.md +++ b/doc/UiNode.md @@ -9,7 +9,7 @@ import 'package:ory_client/api.dart'; Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **attributes** | [**UiNodeAttributes**](UiNodeAttributes.md) | | -**group** | **String** | Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup | +**group** | **String** | Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup | **messages** | [**BuiltList<UiText>**](UiText.md) | | **meta** | [**UiNodeMeta**](UiNodeMeta.md) | | **type** | **String** | The node's type text Text input Input img Image a Anchor script Script | diff --git a/lib/src/model/ui_node.dart b/lib/src/model/ui_node.dart index fbe8686..cc3bbb8 100644 --- a/lib/src/model/ui_node.dart +++ b/lib/src/model/ui_node.dart @@ -16,7 +16,7 @@ part 'ui_node.g.dart'; /// /// Properties: /// * [attributes] -/// * [group] - Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup +/// * [group] - Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup /// * [messages] /// * [meta] /// * [type] - The node's type text Text input Input img Image a Anchor script Script @@ -25,10 +25,10 @@ abstract class UiNode implements Built { @BuiltValueField(wireName: r'attributes') UiNodeAttributes get attributes; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueField(wireName: r'group') UiNodeGroupEnum get group; - // enum groupEnum { default, password, oidc, profile, link, code, totp, lookup_secret, webauthn, passkey, identifier_first, }; + // enum groupEnum { default, password, oidc, profile, link, code, totp, lookup_secret, webauthn, passkey, identifier_first, captcha, }; @BuiltValueField(wireName: r'messages') BuiltList get messages; @@ -178,39 +178,42 @@ class _$UiNodeSerializer implements PrimitiveSerializer { class UiNodeGroupEnum extends EnumClass { - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'default') static const UiNodeGroupEnum default_ = _$uiNodeGroupEnum_default_; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'password') static const UiNodeGroupEnum password = _$uiNodeGroupEnum_password; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'oidc') static const UiNodeGroupEnum oidc = _$uiNodeGroupEnum_oidc; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'profile') static const UiNodeGroupEnum profile = _$uiNodeGroupEnum_profile; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'link') static const UiNodeGroupEnum link = _$uiNodeGroupEnum_link; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'code') static const UiNodeGroupEnum code = _$uiNodeGroupEnum_code; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'totp') static const UiNodeGroupEnum totp = _$uiNodeGroupEnum_totp; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'lookup_secret') static const UiNodeGroupEnum lookupSecret = _$uiNodeGroupEnum_lookupSecret; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'webauthn') static const UiNodeGroupEnum webauthn = _$uiNodeGroupEnum_webauthn; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'passkey') static const UiNodeGroupEnum passkey = _$uiNodeGroupEnum_passkey; - /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup @BuiltValueEnumConst(wireName: r'identifier_first') static const UiNodeGroupEnum identifierFirst = _$uiNodeGroupEnum_identifierFirst; + /// Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup + @BuiltValueEnumConst(wireName: r'captcha') + static const UiNodeGroupEnum captcha = _$uiNodeGroupEnum_captcha; static Serializer get serializer => _$uiNodeGroupEnumSerializer; diff --git a/lib/src/model/ui_node.g.dart b/lib/src/model/ui_node.g.dart index c8bea0c..1d0f4f0 100644 --- a/lib/src/model/ui_node.g.dart +++ b/lib/src/model/ui_node.g.dart @@ -24,6 +24,8 @@ const UiNodeGroupEnum _$uiNodeGroupEnum_passkey = const UiNodeGroupEnum._('passkey'); const UiNodeGroupEnum _$uiNodeGroupEnum_identifierFirst = const UiNodeGroupEnum._('identifierFirst'); +const UiNodeGroupEnum _$uiNodeGroupEnum_captcha = + const UiNodeGroupEnum._('captcha'); UiNodeGroupEnum _$uiNodeGroupEnumValueOf(String name) { switch (name) { @@ -49,6 +51,8 @@ UiNodeGroupEnum _$uiNodeGroupEnumValueOf(String name) { return _$uiNodeGroupEnum_passkey; case 'identifierFirst': return _$uiNodeGroupEnum_identifierFirst; + case 'captcha': + return _$uiNodeGroupEnum_captcha; default: throw new ArgumentError(name); } @@ -67,6 +71,7 @@ final BuiltSet _$uiNodeGroupEnumValues = _$uiNodeGroupEnum_webauthn, _$uiNodeGroupEnum_passkey, _$uiNodeGroupEnum_identifierFirst, + _$uiNodeGroupEnum_captcha, ]); const UiNodeTypeEnum _$uiNodeTypeEnum_text = const UiNodeTypeEnum._('text'); @@ -120,6 +125,7 @@ class _$UiNodeGroupEnumSerializer 'webauthn': 'webauthn', 'passkey': 'passkey', 'identifierFirst': 'identifier_first', + 'captcha': 'captcha', }; static const Map _fromWire = const { 'default': 'default_', @@ -133,6 +139,7 @@ class _$UiNodeGroupEnumSerializer 'webauthn': 'webauthn', 'passkey': 'passkey', 'identifier_first': 'identifierFirst', + 'captcha': 'captcha', }; @override diff --git a/pubspec.yaml b/pubspec.yaml index 2ccf9bf..f3d0e24 100644 --- a/pubspec.yaml +++ b/pubspec.yaml @@ -1,5 +1,5 @@ name: ory_client -version: 1.15.17 +version: 1.16.0 description: OpenAPI API client for Ory Network, Ory's web-scale API for identity and access control. homepage: https://www.ory.sh repository: https://github.com/ory/sdk/tree/master/clients/client/dart diff --git a/test/ui_node_test.dart b/test/ui_node_test.dart index b7d9aca..ab918fe 100644 --- a/test/ui_node_test.dart +++ b/test/ui_node_test.dart @@ -12,7 +12,7 @@ void main() { // TODO }); - // Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup + // Group specifies which group (e.g. password authenticator) this node belongs to. default DefaultGroup password PasswordGroup oidc OpenIDConnectGroup profile ProfileGroup link LinkGroup code CodeGroup totp TOTPGroup lookup_secret LookupGroup webauthn WebAuthnGroup passkey PasskeyGroup identifier_first IdentifierFirstGroup captcha CaptchaGroup // String group test('to test the property `group`', () async { // TODO