Search Results for "want"

...And, if necessary, we should be able to trace this program's detection of HTML errors back to documented best practices or standards, such as W3 specifications. Third-party modules. We want this product to be useful for continuous integration so we prefer to avoid subjective tests which are prone to false positive results, such as spell checkers, indentation checkers, etc. If you want to work on these items, please see the section on custom tests and consider adding an implementation as a third-party module.

This is an implementation of the JSON specification according to RFC 4627. You can think of it as a low-fat alternative to XML if you want to store data on disk or transmit it over a network rather than use a verbose markup language. Both variants of the JSON generator generate UTF-8 character sequences by default. If an:ascii_only option with a true value is given, they escape all non-ASCII and control characters with \uXXXX escape sequences, and support UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. ...

Mobility is a gem for storing and retrieving translations as attributes on a class. These translations could be the content of blog posts, captions on images, tags on bookmarks, or anything else you might want to store in different languages. Storage of translations is handled by customizable "backends" which encapsulate different storage strategies. The default way to store translations is to put them all in a set of two shared tables, but many alternatives are also supported, including translatable columns and model translation tables, as well as database-specific storage solutions such as json/jsonb and Hstore (for PostgreSQL).

...It supports the usual Jekyll workflow (clone the repo, configure _config.yml, build/serve) but enforces AMP constraints (inline CSS, specific tags like <amp-img>, etc). It is ideal for bloggers, personal sites or small static-site deployments who want to publish quickly, benefit from AMP caching/CDNs and focus on readability.

...We're starting simple and avoiding, at least at the outset, all the complications in AMS version, especially all the implicit behavior from guessing the serializer, to the association's serializer, to the serialization type, etc. The basic idea is that models to serializers are a one to many relationship. Everything will need to be explicit. If you want to serialize a User with a UserSerializer, you'll need to call it directly. The serializer will essentially be for defining a basic JSON:API resource object: id, type, attributes, and relationships.

...They are located in templates/. It is also possible to define a custom location for locale definitions. The default one is en.yml, others may be provided as well. This is useful if you want to define new headings.