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

Adds back in a default shadow to CollectionItemViewCell #292

Merged
merged 3 commits into from
Sep 30, 2020

Conversation

simonmitchell
Copy link
Contributor

Description

This adds back in a shadow to collection item view cell that seems to have been removed at the time that blended learning was merged into develop. I can't recall any legitimate reason for this removal, so this PR is re-instating the exact same shadow that was present before

Motivation and Context

Solves shadows not appearing where they should on CollectionItemViewCell

How Has This Been Tested?

Tested running this branch locally in ARC First Aid

Screenshots (if appropriate):

Simulator Screen Shot - iPhone SE (2nd generation) - 2020-09-30 at 13 32 51

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@@ -28,13 +29,25 @@ open class CircleProgressView: UIView {
}
}

/// Apply default shadow configuration
/// Apply shadow configuration based on `shadowComponents` property
public var hasShadow = true {
Copy link
Contributor

Choose a reason for hiding this comment

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

Think we can remove this and just use nullability of ShadowComponents ? 😃

Copy link
Contributor

Choose a reason for hiding this comment

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

Ahh I see your last comment, breaking change... Hmm would just have to handle accordingly in updateShadow as you have.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See my comment on your original comment, the only problem is if we do that it's technically a breaking change... and I'm not a massive fan of doing a major release for something so small after we've literally just made it to v3.0.1 😂

Copy link
Contributor

Choose a reason for hiding this comment

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

Though as it's CircleProgressView wonder if anyone is using hasShadow...

Copy link
Contributor

Choose a reason for hiding this comment

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

But yeah, more than happy to leave 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably nobody, but I want to be strict on ourselves so if we do move to semantic versioning in the future then we're well-practiced at not causing ourselves any headaches :D

@simonmitchell simonmitchell merged commit 74cb83d into develop Sep 30, 2020
@simonmitchell simonmitchell deleted the fix/collectionitemviewcell_default_shadow branch September 30, 2020 12:57
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