-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
dd06dac
to
bbc9a89
Compare
We can do CI instead, or in addition. This is just based on cycle.js and babel which do this in this way already. |
Sure we can add a link here to those packages so it's easy to see. |
@dignifiedquire try to refresh the badges, some of them point to |
See ipfs/js-ipfs#385 for details
We could use an array of packages and do something similar to project-repos.ipfs.io with these, as well. That would remove the necessity to redo the work there, and would allow keeping it up to date easier, I think. |
@RichardLitt I don't see how we can get a markdown table from an array in here, could you explain? |
I'm saying we could specify an array of modules, from anywhere, as things that we want to feed into a variable instance of project-repos.ipfs.io. That way, instead of just seeing IPFS repos, you could switch it to also see the list of js-ipfs submodules. We need to make ipfs/project-repos extensible, anyway, to make sure it works with multiformats and libp2p repositories. cc @harlantwood |
@RichardLitt could you open an issue in @dignifiedquire let's move the "Packages" to right before "Contribute", the list is going to continue growing and we don't want to hide the architecture and descriptions. Also, Thank you! |
why? |
e732445
to
a4d7854
Compare
done |
* test: fix resolve test 1. This is an IPLD path. 2. Resolve really should be resolving up to the last path, not just "failing". * fix: resolve test and add resolve across multiple test License: MIT Signed-off-by: Alan Shaw <[email protected]>
Based on the ideas in #271 and the list from @nginnever I made this package listing.
Closes #271
@diasdavid please review :)