Clojurians Log v2
cljsjs
@miikka Thanks much!!
@jsa-aerial If you have a patch ready to update vega-embed, please submit a PR and let's merge it.
Will do!
OK, done and checks pass. But I see that you went ahead and merged the 3.23.1 - I used my fork as updated to latest CLJSJS before that update, so there are 'conflicts' because the version 3.24.1 is being compared to 3.16.1-1 - same with old vega and vega-lite in build.boot.
@miikka ^^^
OK, in order to prevent this sort of nonsense in the future, I would be willing to be the point person to keep these (the various vega libs) properly updated. I think I saw a place where one can sign up for that but can't find it now. Can you point me to that?
I don't think that I merged any changes to vega-embed? The boot-cljsjs dependency has been updated and that's why there are the conflicts.
I resolved the conflicts now
Maybe you meant this? https://github.com/cljsjs/packages/blob/master/CODEOWNERS
Yes, that looks like what I meant. So, do I just add stuff to that and give PR for it?
OK, sorry, on conflicts it looked like it was complaining about something else - I must have misunderstood. THANKS for the update!
Will do!
OK, done and checks pass. But I see that you went ahead and merged the 3.23.1 - I used my fork as updated to latest CLJSJS before that update, so there are 'conflicts' because the version 3.24.1 is being compared to 3.16.1-1 - same with old vega and vega-lite in build.boot.
@miikka ^^^
OK, in order to prevent this sort of nonsense in the future, I would be willing to be the point person to keep these (the various vega libs) properly updated. I think I saw a place where one can sign up for that but can't find it now. Can you point me to that?
I don't think that I merged any changes to vega-embed? The boot-cljsjs dependency has been updated and that's why there are the conflicts.
I resolved the conflicts now
Maybe you meant this? https://github.com/cljsjs/packages/blob/master/CODEOWNERS
Yes, that looks like what I meant. So, do I just add stuff to that and give PR for it?
OK, sorry, on conflicts it looked like it was complaining about something else - I must have misunderstood. THANKS for the update!