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

User edit dialog expects username #2681

Open
bossenti opened this issue Apr 2, 2024 · 4 comments
Open

User edit dialog expects username #2681

bossenti opened this issue Apr 2, 2024 · 4 comments
Labels
bug Something isn't working good first issue Good for newcomers
Milestone

Comments

@bossenti
Copy link
Contributor

bossenti commented Apr 2, 2024

Apache StreamPipes version

dev (current development state)

Affected StreamPipes components

UI

What happened?

When editing a user in the user management, the dialog expects the user name to be provided.

image

This is an issue since the username is never present when the user was created through self-registration.

How to reproduce?

No response

Expected behavior

No response

Additional technical information

No response

Are you willing to submit a PR?

No, I don't want to submit a PR.

@bossenti bossenti added the bug Something isn't working label Apr 2, 2024
@bossenti bossenti modified the milestones: 0.95.0, 0.97.0 Apr 2, 2024
@muyangye
Copy link
Member

Hey @bossenti! This issue also occurs when some other admins want to edit the initial admin [email protected]. I believe the expected behavior is that the username field is not required right? If so it's just a one-line change. I have found the line but since this change is so simple, maybe we should label it as a good-first-issue so that first time contributors can have a try? If nobody claimes it for say 2 months, I'll push the fix.

@muyangye muyangye added the good first issue Good for newcomers label Apr 27, 2024
@bossenti
Copy link
Contributor Author

Good idea @muyangye, let's do it like that
In addition, we can think of if we want to keep the property Full Name both in the UI and the data model. AFAIK, it is not used currently

@muyangye
Copy link
Member

In my opinion, we should probably keep it despite it's not currently used in code because users might want to know that attribute. For example, an assembly line may have multiple industrial/manufactural engineers who use StreamPipes and they/their admin might be interested in knowing who is who. What do you think?

@bossenti
Copy link
Contributor Author

Yes, I agree. In mid-/longterm we might want to use it, especially if integrating SSO somewhen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants