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

Backported @larryonoff’s gradient line drawing implementation from 4.0 to 3.4 #4327

Closed
wants to merge 1 commit into from

Conversation

Argent
Copy link

@Argent Argent commented Apr 1, 2020

Since the 4.0 branch has been stale for quite a while, but the Gradient Line feature was only implemented there, I decided to back-port it to the 3.4 branch.

All credits for the original implementation go to @larryonoff who developed the feature back in 2018.

Since this is a very important feature for me and I still want to be able to benefit from the improvements that are going on in version 3.x I decided to create a PR to have this feature in the current master branch.

Link to the original PR: #3142

@larryonoff
Copy link
Contributor

Wow. Thanks! This's great

@ChristianVinterly
Copy link

This is great! Alternatively the 4.0 branch could be updated to include the changes to master (#4167)

@Argent
Copy link
Author

Argent commented Apr 6, 2020

This is great! Alternatively the 4.0 branch could be updated to include the changes to master (#4167)

That would be the best option, but 4.0 has been stale for ~2 years. Not sure if anyone is willing to update it with the latest changes. It would need to be someone who was responsible for the initial 4.0 transition and knows the idea behind this refactoring

@liuxuan30
Copy link
Member

liuxuan30 commented Apr 16, 2020

since this feature has been in 4.0 branch, #3415, I don't suggest back port to master. If we merge this, then we have to deal with it while merging 4.0, and it's more chanllenging.

I'd prefer we merge 4.0 soon. @danielgindi @jjatie opinions?
https://github.com/danielgindi/Charts/projects/7, we could remove some open major PRs to future release, I think 4.0 having swift refactor + a few already merged features can be a major release.

@Argent
Copy link
Author

Argent commented Jul 24, 2020

@liuxuan30 are there any updates on the 4.0 merge?

@liuxuan30
Copy link
Member

@Argent could you solve the conflict and make sure CI passes? I do wang to merge 4.0, but since it's a big update, I personally would consider merging some cool features into master first.

@liuxuan30
Copy link
Member

oh wait. 4.0 branch already has line graident, this shouldn't come into master.

@liuxuan30 liuxuan30 closed this Jul 27, 2020
@liuxuan30
Copy link
Member

I don't get feedback about merging 4.0 from other peers. I will need to address it whey they have time to work on this.

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