-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Is chartsian library down? #1
Comments
Same here, missing here version 7.2 |
Indeed - v7 is down for now, but will be back up. If you're wondering why - the author got slapped with a trademark violation notice. See this Twitter thread for more info. It's a horrible thing to happen to you as an OSS maintainer, to have legal action threatened against you, when your only intention was to build free stuff for people. So please be mindful. What I get from what Erik said:
|
Same here, any workaround? |
|
Hey guys, sorry for all the trouble. As @tabacitu said, I got a trademark notice for the v7 / chartisan project. Therefore I had to shut down the entire project. The charts repository was indeed affected as well. For the time being, I was able to get the Charts repository created after getting in touch with github (and lost all stars, tags and commits). Therefore I could only publish v6. V7 will never be recovered. Instead, I have already started working on what would have been v8. But I think this will be left in a new package. I will have more information on that as time moves on. In the meantime, thanks a lot for the support. I am deeply sorry for v7 users, but there's no way I can republish that without dealing with namespace issues (where the trademark would apply). To be fair, anybody with the v7 version are actually in danger as well as the trademark could be used against them. So that's why I had decided to just shut it down. Not only to protect myself but also businesses and individuals using it. |
And where's the api link for v6, the project keep crushing cause the api link in the composer.lock file. |
What's an API link? The docs are here: https://charts.erik.cat/ |
The v6 of this library does not involve anything related to the project |
{ |
The repository was changed to https://github.com/ConsoleTVs/Charts instead of https://github.com/Chartisan/Charts to avoid copyright claims. Please update your composer lock file! |
Okay I'll, and the other link, please find solution for that too. |
There is not going to be a solution. That package is using a trademarked name on the source code level. It is not coming back. |
What can we do to be supportive or helpful with getting v8 developed, tested and available? |
Guys, I am using 6 but it is no longer working. Any ideas? |
@juanitocbsi what do you mean by "no longer working"? |
Thanks! My pipeline is no longer deploying v6. I get a 404. |
Hi I tried to run this command |
Does it work after you run |
@ConsoleTVs anything we can do to help with v8 get backup online? production projects are massively failing. |
You mean v7? No. It will never be online again. It was using a trademarked name in the source code. There's no way to fix that. As for a new release, it is possible we get a new version of this sooner or later. But the v7 won't come back. |
Thanks, @ConsoleTVs for the response. To be clear, I meant v8, do you have a timeline in mind? I have some spare time and would love to be of help. |
@ConsoleTVs Maybe a dumb question, but is it not possible to simply find and replace the name in the whole source code? I mean the code base was really great, quite a significant number of projects was using it, and just only in this ticket we are already 3 people to offer our help to sort this out. |
It's a breaking change. Requires both, package name changes and namespace changes, therefore it is not really worth because the fix won't be easy and require changes to codebases, so there's no real benefit that I can see here. (and keep in mind this changes are also on the frontend packages as well, so a real mess here)
I am working on it on my spare time already. But I don't want to risk myself on saying timelines. I will for sure notify everybody using this lib when this happens as best as I can (twitter, here, readme, docs, etc). |
sounds like you might have some people that are willing to help. Could you create a private git ,and invite people that are interested in helping? |
There is a workaround that can be quickly set up for v7 users, in order to continue to use the package as is, as long as the v8 has not been released :
"repositories": [
{
"type": "path",
"url": "./packages/consoletvs/charts"
},
{
"type": "path",
"url": "./packages/chartisan/php"
}
], The copied sources should be now used instead of the packagist or github ones. |
Are they any docs on downgrading from 7 to 6 ? Does not seem as simple as just requiring the old package. |
If I do recall correctly, v7 was a huge change of direction from v6, v6 didn't use Chartisan at all (pls no lawyers) and instead worked with ChartJS, FusionCharts, ECharts etc etc. What I'm trying to say is it wasn't just a version bump with some new features but almost a complete rewrite which will require you to re-work everything you did. If anyone is interested, there isn't really a solid alternative to quickly generating charts in Laravel, I was thinking of creating something similar to V6 using exclusively ApexCharts |
I was using version 7 and now I want to downgrade to 6 before you release version 8. I am getting the following error: In Version 7 I was registering the charts in the AppServiceProvider Class using the ConsoleTVs\Charts\Registrar what do I need to do now? |
Any idea when v8 will be released? |
We noticed that our pipeline is failing, it depnds on ConsoleTVs/Charts, which in turns depend on chartisan/php library.
The github chartisan account is not accessible 404, do you know if there is any work around ?
The text was updated successfully, but these errors were encountered: