Skip to content
#

crates

Here are 225 public repositories matching this topic...

Jake-Shadle
Jake-Shadle commented Apr 22, 2021

In the docs, there are several cases such as here where code snippet examples are shown side by side, without actually specifying which files they are (eg. deny.toml vs Cargo.toml) which can lead to confusion for users. Every code snippet should just specify # <name>.toml at the top for clarity.

martinmake
martinmake commented Nov 8, 2020

It is a very exciting Authorization Flow for developers of server-less applications that use Spotify API directly.

Not only will the users of these applications no longer have to setup their own Spotify Applications,
but also the creators will get to see usage metrics of their applications in their Spotify Dashboard.

You can find out how it works [here](https://developer.spotify.com

Hirevo
Hirevo commented Oct 13, 2019

This is a tracking issue for additional Store implementations.

Here is a non-exhaustive list of potential candidates for an Store implementation:

  • S3Storage:
    This would store crate tarballs and rendered README pages into Amazon's S3.
  • RemoteStorage:
    Requires to implement a companion server.
    The idea is to have a reserved folder on another machine which runs a comp
notriddle
notriddle commented Oct 24, 2017

As nice as it is to be able to remove the blatantly bad stuff, sometimes you don't want the user to be able to enter any HTML at all. You could do this by escaping the markup, but if having a database with &lt; in it doesn't appeal to you, or you're worried about double-escaping or similarly nasty accidents, you could use a function that just tells you if a string has any HTML tags in it. And in

Improve this page

Add a description, image, and links to the crates topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the crates topic, visit your repo's landing page and select "manage topics."

Learn more