<commit_before>flask_restify
=============

Accept-sensitive translation wrapper for Flask views.

Why?
====

Have you had instances where you wanted to adjust your representation
based on the requested content type?  Typically, in Flask this amounts to
an if-wrapper around the various representation generators.  However,
in most cases this is largely boilerplate.  Ideeally, the controller
function would return an entity and serializers would convert that to a
string form (see RESTlet and Catalyst::Controller::REST for examples from
other languages).

Simple Example
==============

In the app setup:

    from flask_restify import RESTify
    
    RESTify(app)
<commit_msg>Corrected Why docs<commit_after>flask_restify
=============

Accept-sensitive translation wrapper for Flask views.

Why?
====

Translating an entity to a representation is often boilerplate.  This
module aims to remove that boilerplate by allowing view functions to simply
return a generic entity and letting restify() figure out what sort of
conversion function to call based on the Accept header.

Simple Example
==============

In the app setup:

    from flask_restify import RESTify
    
    RESTify(app)

{'fraction_non_alphanumeric': 0.08235294117647059, 'fraction_numerical': 0.0, 'mean_word_length': 4.781553398058253, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4949893', 'n_tokens_mistral': 316, 'n_tokens_neox': 289, 'n_words': 147}