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

Optionset Provider Depending on User #430

Closed
m6121 opened this issue Mar 17, 2022 · 3 comments
Closed

Optionset Provider Depending on User #430

m6121 opened this issue Mar 17, 2022 · 3 comments

Comments

@m6121
Copy link
Member

m6121 commented Mar 17, 2022

Extending the optionset provider interface so that this includes the current user in addition to the project and search information might enable new usage scenarios. The idea is that another non-public service is queried depending on the user and the result is used as dynamic optionset.

@jochenklar
Copy link
Member

Yes, I like it. Maybe we should just generally hand over the request object to plugins. We can then also get rid of the search parameter here.

@jochenklar
Copy link
Member

Adding the full request to the provider or replacing the search parameter might raise compatibility issues, so I just added the user (and the site, because why not). Other information from the request does not seem nessesary.

jochenklar added a commit that referenced this issue Jul 8, 2024
…ns_provider

Add user and site to options provider (#430)
@jochenklar
Copy link
Member

Will be part of RDMO 2.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants