Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make credentials purpose required #84

Open
thclark opened this issue Jun 2, 2021 · 0 comments
Open

Make credentials purpose required #84

thclark opened this issue Jun 2, 2021 · 0 comments
Assignees
Labels
feature A new feature of the app

Comments

@thclark
Copy link
Collaborator

thclark commented Jun 2, 2021

Feature request

Use Case

In the credentials strand, the purpose field is not required, just the credential name. We discussed in this PR that it would be sensible to make purpose required.

It should be a unicode character field of up to 120 characters. I suppose the actual character string could be blank, but have the field always present.

Current state

In the examples we're providing a purpose field all the time anyway, and think it's best practice to properly describe the entry so that should be reinforced to support good UX

@thclark thclark added experience (UX) feature A new feature of the app labels Jun 2, 2021
@thclark thclark removed this from Octue Board Dec 1, 2021
@thclark thclark moved this to Priority 2 (Medium) in Octue Board Dec 1, 2021
@thclark thclark moved this from Priority 2 (Medium) to Priority 1 (Low) in Octue Board Dec 1, 2021
@thclark thclark removed the schema label Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature of the app
Projects
Status: Priority 1 (Low)
Development

No branches or pull requests

2 participants