Skip to content
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.

Selected environment should preserve on project selection #23

Open
d-gs opened this issue Oct 8, 2021 · 0 comments
Open

Selected environment should preserve on project selection #23

d-gs opened this issue Oct 8, 2021 · 0 comments
Labels
Hacktoberfest Prio: Low New feature or request Status: Accepted Issue or PR is accepted Type: Feature Issue or PR is a new feature

Comments

@d-gs
Copy link
Member

d-gs commented Oct 8, 2021

Feature request

Expected Behavior - What were you expecting to happen?

Currently, if on the Project dropdown the environment have a counterpart on the Environment dropdown, the second should be preserved on project selection. For example, imagine 2 projects called GEM and the other Custom GEM, both with environments v1 and v2. If GEM / v2 is selected, and then the project is switch to Custom GEM, the Environment should be kept to v2.

Current Behavior - What happens?

Currently, in the previously described example, on project selection for Custom GEM the Custom GEM / v1 environment is selected. Although for some use cases it makes sense that this happen, it might be that the version number for 2 different projects have nothing to do with each other so jumping to the first project is the correct solution. This should also be taken into account for the possible solution.

Possible Solution

The solution is simple as keeping the environment if it exists by comparing the environment ID might be easy. This will enforce configurations to keep the same ID for the environments if they want to enable this behavior for some of them and/or prefix the ID if they want to keep it independent.

Context

User experience. E.g., in the case of related projects with similar versioning this makes sense for the user that otherwise is jumping always to the upper version of an environment.

Notes and further information

Low priority as it doesn't affect important behavior but user-experience on a use-case of configuration of projects/environments.

@d-gs d-gs added Prio: Low New feature or request Status: Accepted Issue or PR is accepted Type: Feature Issue or PR is a new feature Hacktoberfest labels Oct 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Hacktoberfest Prio: Low New feature or request Status: Accepted Issue or PR is accepted Type: Feature Issue or PR is a new feature
Development

No branches or pull requests

1 participant