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

[frontend] Remove useless scenario filter in the overview of a scenario #2185

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

savacano28
Copy link
Contributor

@savacano28 savacano28 commented Jan 9, 2025

Proposed changes

  • Remove scenario filter and add name exercise

Screenshot 2025-01-09 164552

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality
  • For bug fix -> I implemented a test that covers the bug

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@savacano28 savacano28 self-assigned this Jan 9, 2025
@savacano28 savacano28 added the filigran team use to identify PR from the Filigran team label Jan 9, 2025
@savacano28 savacano28 marked this pull request as ready for review January 9, 2025 15:51
@savacano28 savacano28 force-pushed the bugfix/1672-release branch from e406889 to b7ad5fd Compare January 9, 2025 15:52
@savacano28 savacano28 merged commit b635306 into release/1.11.0 Jan 9, 2025
4 checks passed
@savacano28 savacano28 deleted the bugfix/1672-release branch January 9, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants