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

Docs: Improve documentation and enhance Trial story UX #1450

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

drikusroor
Copy link
Contributor

Add docstrings for style constants in styles.py for better clarity. These don't seem to show up in mkdocs though... Maybe because they aren't classes/functions?

Fix the initial display issue of the Trial story to improve user experience by ensuring it shows correctly without requiring a click.

Related to #1428

@drikusroor drikusroor self-assigned this Dec 27, 2024
@drikusroor drikusroor mentioned this pull request Dec 27, 2024
26 tasks
@drikusroor drikusroor added the documentation Improvements or additions to documentation label Dec 30, 2024
Copy link
Collaborator

@BeritJanssen BeritJanssen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, styles is something to be revisited. I see two approaches now:

  • a dictionary with multiple 'class-name': True combinations, which essentially means these classes will be slapped onto the class list of the corresponding frontend component's element. This is used in the Categorization rules.
  • a single string, which is evaluated by FrontendStyle against a number of possible values.

I like the first approach better, as it's less involved. However, I also struggle with how to document the possible class names that could be set from the backend, and their effect on the frontend styling. It would be good that, if a user sets the class name to neurtal, the backend raises a warning to catch the typo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants