Move guides to libraries where appropriate #96
Comments
|
Aside from the license issue we discussed, I think it's a great idea. |
|
I'll check the git history to get a list of contributors to those. |
|
I think this is complete. I've done my best to go back through the histories in both this repo and the website one: Partial: hdgarrood |
|
Also kika on the generics one. Seems like eff will be the trickiest one, but the others should be simple enough to deal with. I think we need a CONTRIBUTORS.md file going forward, until we can get to the point where we can add a LICENSE file. |
hdgarrood
changed the title
|
Is anything stopping us from moving this forward? If not, I'll create the PRs in the library repos. |
|
I don't think so, please do! |
|
Everyone listed above is now in CONTRIBUTORS.md 🎉 |
Link to the purescript-partial library instead, which is where the guide now lives.
Link to the purescript-partial library instead, which is where the guide now lives. I've kept this page for now instead of removing it completely, because the compiler's Prim docs page still links to it as of 0.12.2 (see: <https://pursuit.purescript.org/builtins/docs/Prim#t:Partial>)
Link to the purescript-partial library instead, which is where the guide now lives. I've kept this page for now instead of removing it completely, because the compiler's Prim docs page still links to it as of 0.12.2 (see: <https://pursuit.purescript.org/builtins/docs/Prim#t:Partial>)
I think some guides would probably be easier to find if they were put in the docs for the relevant libraries. For example:
purescript-partialpurescript-quickcheckpurescript-eff(actually moved topurescript-effect)purescript-generics-repI also think they'd be less likely to go out of date, as you're more likely to remember to update guides like this if they're right there when you're changing the code.
What do people think?
The text was updated successfully, but these errors were encountered: