You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest making a new section of facades that are self contained in a single gist, or possibly also, for incomplete/nascent repos. Some JS libraries may have rather incomplete facades, or only need a gist. Rather than going through the whole dependency management and publication issue, a gist that can be copied in and modified would be useful. I think it would still be valuable to have a centralized list of such gists, perhaps as a wiki page that doesn't require constant review.
The text was updated successfully, but these errors were encountered:
Interesting idea, but the thought of having to copy-paste code is discomforting. I wonder if it'd make more sense to have a shared project for an "initial" phase of facades, before they decide to live in a separate repository?
The real underlying issue here is the tough time we have publishing things with SBT to Maven Central via its cumbersome process. Of course it's possible to include libraries as Git dependencies as well though that's not particularly clean. I recall seeing a Scala community article/comment somewhere suggesting a more lightweight approach to publishing libraries.
Jitpack (https://jitpack.io) looks nice but I haven't seen too many people use it.
I suggest making a new section of facades that are self contained in a single gist, or possibly also, for incomplete/nascent repos. Some JS libraries may have rather incomplete facades, or only need a gist. Rather than going through the whole dependency management and publication issue, a gist that can be copied in and modified would be useful. I think it would still be valuable to have a centralized list of such gists, perhaps as a wiki page that doesn't require constant review.
The text was updated successfully, but these errors were encountered: