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

925 - Routing Styling Changes #554

Merged
merged 1 commit into from
Aug 5, 2019
Merged

925 - Routing Styling Changes #554

merged 1 commit into from
Aug 5, 2019

Conversation

hamishtaplin
Copy link
Contributor

@hamishtaplin hamishtaplin commented Aug 2, 2019

What is the context of this PR?

Updates routing UI to meet latest designs:

  • added "match" UI for upcoming AND/OR changes
  • moves add/remove BinaryExpressionEditor buttons inline
  • added dropdown for selecting answer/metadata/variable in prep for new content picker
  • fixed some missing transitions
  • some styling changes

Other changes:

  • removed TabBody component from EditorLayout/Tabs—replaced usage with generic Panel component.

How to review

  • Can still add/remove routing rules
  • Can still add/remove BinaryExpressionEditor instances
  • No styling bugs introduced in radio/number routing UIs

@hamishtaplin hamishtaplin force-pushed the routing-update-design branch from 07b7a05 to a39ebab Compare August 2, 2019 07:45
Copy link
Contributor

@pricea1 pricea1 left a comment

Choose a reason for hiding this comment

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

A couple of comments but otherwise LGTM

<option value="all" selected>
All of
</option>
<option value="any" disabled>
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it worth making it more obvious its disabled until its functional? To me, it looked as though All of was in bold because its selected and Any of was a selectable option. Same for Answer/Metadata option.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fair point 👍

@@ -154,6 +155,7 @@ Resolvers.Mutation = {
}, pages);

const routing = page.routing;

Copy link
Contributor

Choose a reason for hiding this comment

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

This file hasn't been modified and can be removed from commit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

idk why it's included or how to remove!

Copy link
Contributor

Choose a reason for hiding this comment

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

Just remove the newlines on 149 and 158 and commit again.

Copy link
Contributor

@heofs heofs left a comment

Choose a reason for hiding this comment

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

Looks good just a couple of comments.

@heofs heofs force-pushed the routing-update-design branch from 686e1ef to f59e3a1 Compare August 5, 2019 11:10
@heofs heofs merged commit 50ecd6a into master Aug 5, 2019
@samiwel samiwel added this to the v0.30.0 milestone Aug 5, 2019
@martyncolmer martyncolmer deleted the routing-update-design branch August 13, 2021 08:55
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.

4 participants