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

Some small progress redesign fixes #13935

Merged
merged 9 commits into from Mar 23, 2017
Merged

Some small progress redesign fixes #13935

merged 9 commits into from Mar 23, 2017

Conversation

Bjvanminnen
Copy link
Contributor

Poorva did a pass of the progress redesign stuff, and came up with a big list of small things. This addresses some of them.

image

  1. Locked stages don't get numbered (previously this would have had the assessment as Lesson 1, and the first lesson as Lesson 2).
  2. Hidden/lock icons come after the collapse icon instead of before it.

image
image
3. In both summary and detail view, when viewing as teacher don't make hidden/lockable stages opaque.
4. In both summary and detail view, don't disable bubbles when viewing as teacher. This way we still get the hover behavior of the bubble turning orange.

@@ -66,12 +67,12 @@ const ProgressBubble = React.createClass({
href = url + location.search;
}

const tooltipId = _.uniqueId();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was done because in storybooks we end up with multiple bubbles that have the same URL (even though I think this should never happen on a real page). I alternatively could have tried doing the work to make our storybooks always provide unique urls, but this approach seems more resilient.

description={"At some point we reach a physical limit of how fast " +
"we can send bits and if we want to send a large amount of " +
"information faster, we have to finds ways to represent the same " +
"information with fewer bits - we must compress the data."}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't actually use description anywhere right now, so it seems silly to have a storybook for it.

* @param {ViewType?} viewAs - Optional param to determine whether the lesson
* would be visible if viewing as someone else
* @param {ViewType} viewAs - Are we interested in whether the lesson is viewable
* for students or teachers
* @returns {boolean} True if the provided lesson is visible
*/
export function lessonIsVisible(lesson, state, viewAs) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Previously we would call this method sometimes providing a viewAs, and sometimes not (in which case we would default to whatever was currently in the redux store). This was confusing, and I never really liked it. Now that SummaryProgressRow has viewAs as a prop (which will be the same as whatever is in the redux store), it's cleaner to just always pass in the viewAs prop and not have this as an optional param.

@caleybrock
Copy link
Contributor

read through all of this and don't have any questions - thanks for making logical commits and useful commit messages. I assume since I'm on assignee and not reviewer, you're adding another person, but it all makes sense to me.

@Bjvanminnen
Copy link
Contributor Author

I'm not really sure of the difference between assignee/reviewer and don't really differentiate personally. Was not planning to assign anyone else :)

@caleybrock
Copy link
Contributor

cool, well LGTM then 👍

@Bjvanminnen Bjvanminnen merged commit ba37322 into staging Mar 23, 2017
@Bjvanminnen Bjvanminnen deleted the progressFixes branch March 23, 2017 20:24
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.

None yet

2 participants