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

Provide way to change context (package / top-level) in Web UI #280

Closed
isc-tleavitt opened this issue Sep 3, 2023 · 1 comment · Fixed by #456
Closed

Provide way to change context (package / top-level) in Web UI #280

isc-tleavitt opened this issue Sep 3, 2023 · 1 comment · Fixed by #456
Assignees
Labels
enhancement New feature or request

Comments

@isc-tleavitt
Copy link
Collaborator

Use case:
IRIS BI editors - specifically the user portal - are misbehaving and not launching the web UI for some reason. (The page just reloads.)* As a workaround, I should be able to go back to the home page and get to the Git WebUI for my own package (or the top-l;evel repo for the namespace).

If the Web UI is launched without a context, it should help the user select one based on valid configuration: top level (if namespace temp folder has .git) and any git-configured packages. It should also be possible to change context after the fact.

*I don't know what the cause is, that's a separate issue (encountered in my development environment for a personal side project). $zv is IRIS for Windows (x86-64) 2022.3 (Build 606U) Mon Jan 30 2023 09:12:22 EST.

@isc-tleavitt
Copy link
Collaborator Author

@isc-tleavitt to provide a class query that works for IPM 0.7.x and 0.9.0 to do the right things here - we need to get, given a namespace, all the names of packages that were loaded from git repos. (That is, they're in DeveloperMode and have a .git folder under the package Root folder.)

@isc-hwojnick to do the UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants