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

Consolidating open PRs #40

Merged
merged 6 commits into from
Sep 13, 2018

Conversation

reedmclean
Copy link
Contributor

I wanted to pull in the good contributions from open PRs that we haven't addressed in the last couple of years. A good chunk of them have changes that I think would benefit the library, but they've been left open for long enough that I think the interest in fixing them has significantly waned. They either have changes requested of them or conflicts with master, so instead of individually checking out each branch, applying the fixes, and opening new PRs for each of them, I cherry-picked the relevant commits, applied necessary changes, and combined them into this PR. This will let us pull in contributions and close out the majority of open PRs.

This PR (along with #23, which I merged this morning) also represents the features that I think should be included in the next minor version. There are a couple things that I would really like to pull into this library (#30 and #39 are frontrunners), but they would involve backward-incompatible changes that would require us to increment the major version before releasing. These changes possibly include incrementing the minimum Framework version up to 4.5, so I'd like to include as many features as possible before introducing breaking changes.

I'm hoping that the commits are distinct enough to make reviewing this relatively painless. On the other hand, this is a single PR covering multiple features, so I understand if it would be easier to review if it was split into separate PRs. Let me know if that's preferable, and I can do that.

reedmclean and others added 6 commits August 9, 2018 15:44
public List<InteractionComponent> scale { get; set; }
public List<InteractionComponent> source { get; set; }
public List<InteractionComponent> target { get; set; }
public List<InteractionComponent> steps { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

It will probably become a need pretty quickly to allow for individual additions of a single InteractionComponent to each of these lists. The public interface of the class requires you to set the whole list. That's been an issue elsewhere in the library in the past. Not something that has to hold up this PR, but it is something to be aware of for the future.

@brianjmiller
Copy link
Member

@reedmclean go with it, I'll let you do the honors and cut the release. If you need assistance with that, let me know.

@reedmclean reedmclean merged commit 27262b3 into RusticiSoftware:master Sep 13, 2018
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.

5 participants