recentpopularlog in

kme : spec   19

RFC 4180 - Common Format and MIME Type for Comma-Separated Values (CSV) Files | https://tools.ietf.org/
(2.5) Each field may or may not be enclosed in double quotes (however some programs, such as Microsoft Excel, do not use double quotes at all). If fields are not enclosed with double quotes, then double quotes may not appear inside the fields.

(2.7) If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote.
rfc  csv  format  spec  commaseparated  delimitedfile  fileformat  reference 
april 2019 by kme
apiary.io - How can I have multiple responses from a single endpoint with different parameters? - Stack Overflow [http://stackoverflow.com/]

12
down vote
To document multiple responses simply add it after the Response 200 like so:

## Thing [/thing/{id}]
Gets a thing but the thing id must be a prime number!

+ Parameters
+ id (string) ... ID of the thing, a prime number!

+ Model (application/json)

The thing itself.

+ Body

{
"description": "It is green"
}

### Retrieve a Single Gist [GET]
+ Response 200

[Thing][]

+ Response 400 (application/json)

{ "error" : "Invalid request" }
Note there is currently no dedicated syntax to discuss the conditions (when this response i s returned). You can discuss it anyway you like it for example:

+ Response 400 (application/json)

This response is returned when no `Thing` for given `id` exists.

+ Body
If you are using Apiary mock, keep in mind that the first response listed is returned by default, unless you say otherwise using the prefer HTTP header.
apiary  rest  api  spec  blueprint  useful 
march 2017 by kme
Debian Policy Manual - Control files and their fields
5.6.12 Version

The version number of a package. The format is: [epoch:]upstream_version[-debian_revision]


The "Revision:" in the controlfile seems to be ignored now; even Vim didn't syntax highlight it.

I tried putting it a version number like '1.2.3-mine1' in 'debian/changelog' and that worked. You get this warning[1], but it seems harmless. You can't use something like '+mine1' because that's considered part of the "upstream" release number, and so the tarball needs to have the same name.

[1] https://lintian.debian.org/tags/source-nmu-has-incorrect-version-number.html
debian  apt  packaging  packagemanagement  spec  guide  solution 
june 2016 by kme

Copy this bookmark:





to read