pursuit
pursuit copied to clipboard
Website for hosting and searching PureScript API documentation
For example, @thimoteus pointed out in Slack that [a search for ](https://pursuit.purescript.org/search?q=%3C%24%3E) works fine, but [a search for ()](https://pursuit.purescript.org/search?q=%28%3C%24%3E%29) gives none of the desired results. They should probably yield the...
For example, in the type signature for `forever`, the -> is broken across lines:  I only want to do this if it can be done without affecting your ability...
Going by the [help page for Pursuit](https://pursuit.purescript.org/help/users#searching) my best guess for finding functions that return something of type `HTMLElement` was `HTMLElement` or `a -> HTMLElement`. Neither gives any results although...
One way to resolve issues similar to #392, #382 and #335 once and for all is to give up on the ability to upload packages directly and just reuse package-sets...
The simplest way would be to leverage github search, but we can get much better result if we add to pursuit the source code, or just the mapping from `IdentifierName...
Looks like `pulp publish` will overwrite a previous package by the same name. Happened to me right now when I published https://github.com/jacereda/purescript-benchmark There was already a package on Pursuit: https://github.com/cyrbon/purescript-benchmark
Suggestion from @joneshf. Now that instance docs are displayed, it makes a lot more sense to provide a (#) link which points to a specific instance, for sharing the URL....
I have forked TinkerTravel/purescript-modules and renamed repo, but forgot to change “name” in bower.json. so i made pulp release and new release was made but for original module, see https://pursuit.purescript.org/packages/purescript-modules/4.0.0...
I think it would be really cool if the functions would be listed on the right as well. Then you could see at a glance which functions are exposed by...