Open FlorianJacta opened 5 months ago
Hi, can I work on this?
Sure! @ovindu-a
Thank you for your contribution.
Hi @jrobinAV, quick question. Could you tell me if there is a way I can test the changes once I make them?
Hi @ovindu-a ,
I believe @namnguyen20999 @FredLL-Avaiga @FabienLelaquais @dinhlongviolin1 would be the right persons to help you on the UX side.
Hi, @namnguyen20999 , @FredLL-Avaiga , @FabienLelaquais , @dinhlongviolin1 if possible could someone let me know how to test the changes I make in the ui? I think I can close this issue if I figure it out.
we have tests in backend (python: pytest), frontend (typescript: jest) and end-to-end (python: playwright) You can look at the existing tests related to the files you impact.
A new Quest has been launched in @Avaiga’s repo. Merge a PR that solves this issue to loot the Quest and earn your reward.
Some loot has been stashed in this issue to reward the solver!
🗡 Comment @quest-bot embark
to check-in for this Quest and start solving the issue. Other solvers will be notified!
⚔️ When you submit a PR, comment @quest-bot loot #1403
to link your PR to this Quest.
Questions? Check out the docs.
@quest-bot embark
@ovindu-a has embarked on their Quest. 🗡
HTML
and Shell
magic ✨Questions? Check out the docs.
@FredLL-Avaiga is there a way that I can run the frontend so I can see the changes that I make. I'm having an issue figuring out how to do that by following the docs.
Of course, yes so the process is:
Then create a simple python script that shows your new feature or bug fix (something like doc\gui\examples\controls\button_action.py or others) run the script you can debug in the browser
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.
@ovindu-a I don't see any PR linked to this issue. Are you still working on this ? Do you plan to propose a PR soon ?
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.
Description
The UX of creating filters could be better in the Data Node/Scenario selector. It would be better to propose something like this:
Providing a default "action" for each filter would enhance the filter UX. For example, the tags filter could have as a default action: "contains". Right now, you need a lot of clicks to get the filter in place.
Code of Conduct