Feat/experiment_manager

[ihsanKisi]

📥 Pull Request Description

This pull request implements the experiment manager feature. This feature was requested to be able to filter experiments based on their properties.

👀 Affected Areas

Experiments

📝 Checklist

Please make sure you've completed the following tasks before submitting this pull request:

• Pre-commit hooks were executed
• Changes have been reviewed by at least one other developer
• Tests have been added or updated to cover the changes (only necessary if the changes affect the executable code)
• All tests ran successfully
• All merge conflicts are resolved
• Documentation has been updated to reflect the changes
• Any necessary migrations have been run

📌 Related Issues

[Feature]: We have to manage the experiments in the dashboard. #2

🔗 Links

Please provide any relevant links (e.g. documentation, external resources) that support your changes.

📷 Screenshots

Without filtering (10 experiments):

With filtering by experiment_type:

[aiakide]

Please merge the current develop branch. Please pay attention to which files you commit. Not everything should be added to the repo.

[github-actions]

Coverage Report •

File	Stmts	Miss	Cover	Missing
__init__.py	1	0	100%
dashboard.py	13	13	0%	11–13, 17, 20, 25, 32, 34, 38–39, 42, 44–45
exceptions.py	1	0	100%
basecomponents
sidebar.py	11	11	0%	13, 15, 17–18, 21, 24, 33, 36, 38–39, 48
table.py	9	9	0%	12–16, 19–20, 30, 34
basecomponents/buttons
__init__.py	0	0	100%
sidebarbutton.py	11	11	0%	4–5, 7, 14, 19, 32–34, 36–37, 40
sidebartogglebutton.py	29	0	100%
experiment
experimentmanager.py	15	8	46%	21, 33–36, 41, 43, 48
pages
home.py	23	23	0%	13, 16, 22–25, 28–29, 34–38, 40–41, 43–50
state
__init__.py	0	0	100%
appstate.py	36	36	0%	7–9, 11–13, 15, 17, 20, 26, 31, 33, 37, 39, 49–50, 52–54, 57, 67–70, 73, 81–86, 89, 95, 100, 103, 108
TOTAL	232	121	47%

Pytest summary

Tests	Skipped	Failures	Errors	Time
11	0 💤	0 ❌	0 🔥	5.332s ⏱️

[aiakide]

Please have a look at the comments. We can talk about it again.

[aiakide]

Please use a more appropriate class name. This is where our app data is stored. I qould suggest something like State, or AppState.