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

Add all missing analyses config fields #426

Merged
merged 2 commits into from
Feb 7, 2023

Conversation

JosephMarinier
Copy link
Contributor

Description:

Add to the config page all the fields that were missing from the syntax, similarity, and behavioral testing sections.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

  • ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
  • PRE-COMMIT. You ran pre-commit on all commits, or else, you
    ran pre-commit run --all-files at the end.
  • USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
    our users.
  • DEV CHANGES.
    • Update the documentation if this PR changes how to develop/launch on the app.
    • Update the README files and our wiki for any big design decisions, if relevant.
    • Add unit tests, docstrings, typing and comments for complex sections.

@nandhinibsn
Copy link
Contributor

True. this is simpler. I think we can apply these changes.

Copy link
Contributor

@nandhinibsn nandhinibsn left a comment

Choose a reason for hiding this comment

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

Just one question, Changing it to flex won't shrink the content when we scroll?

@@ -551,6 +557,7 @@ const Settings: React.FC = () => {
{displayToggleSectionTitle("similarity", "Similarity")}
{getAnalysesCustomization("similarity")}
{displayToggleSectionTitle("behavioral_testing", "Perturbation Testing")}
{getAnalysesCustomization("behavioral_testing")}
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we not hide the section if behavioral testing is null? Do we display default config values if it's null?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, I was waiting for your input here before changing that. What do you think?

Copy link
Contributor

@nandhinibsn nandhinibsn Feb 7, 2023

Choose a reason for hiding this comment

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

Okay, I'm so sorry I did not respond there. Yes, I do prefer hiding the content; but we disable in similarity and postprocessor. I can handle that disabling part if we are going to follow the pattern of similarity and postprocessor

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No worries!
Right, showing the default values, but grayed out, is also interesting. You have done it for similarity and postprocessor fields, except it doesn't work for read-only fields.
image
We could fix that. Or we can hide. Maybe we can ask the team in standup tomorrow?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, sure, we can ask for clarification. True, disable feature is not added to the read-only part.

webapp/src/pages/Settings.tsx Outdated Show resolved Hide resolved
@JosephMarinier JosephMarinier merged commit 328cb2b into main Feb 7, 2023
@JosephMarinier JosephMarinier deleted the joseph/add-missing-analyses-config-fields branch February 7, 2023 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants