| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
It now actually looks at the fields which have been provided.
|
| |
|
|
|
|
| |
As previously the pages would render, but with no data.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Where there are multiple interrelated fields, then it's useful to only apply
the default if another field hasn't been specified.
|
| |
|
|
|
|
| |
Particularly to support checkboxes.
|
| |
|
|
|
|
| |
Mostly to enable passing the cache-control header.
|
|
|
|
|
|
| |
Given that the headers may be the same, regardless whether it's HTML or JSON
being sent in the body of the response, I think it makes more sense to handle
the headers in the controller.
|
| |
|
|
|
|
|
| |
To get git repository and git branch information suitable for the revision
page.
|
|
|
|
| |
This is useful for some queries with duplicated parts of the results.
|
|
|
|
| |
Date and Commit were the wrong way around.
|
| |
|
| |
|
|
|
|
|
| |
This is mostly for the JSON output, as it allows much more information to be
included.
|
|
|
|
| |
To the query parameters module.
|
| |
|
|
|
|
|
| |
Previously, the timezone was stripped off, so the timestamps were off. This
commit changes the code to use a Unix timestamp, which avoids this issue.
|
|
|
|
|
|
|
|
|
|
| |
And display this on the package page.
This uses a couple of new tables, and an additional field in the
package_metadata table.
Currently, the order of the licenses in the package definition isn't stored,
as I'm not sure the order in the list is significant.
|
|
|
|
|
|
|
|
| |
On one code path, they were handled as numbers, whereas elsewhere they were
handled as strings. This led to the package-metadata code trying to insert
duplicate entries.
Instead, just handle them as strings everywhere.
|
|
|
|
| |
So at least they're stable.
|
|
|
|
|
|
|
| |
Store the location a package can be found at, and display this on the package
page.
If available, link off to the git repository containing the package.
|
| |
|
|
|
|
|
| |
This allows building more complicated forms, where some of the query
parameters don't work together.
|
| |
|
|
|
|
|
| |
Lower powered devices will have problems displaying all ~9000+ packages, so
return a smaller number by default.
|
|
|
|
|
|
|
|
| |
I'm thinking about adding more fields to this table, and the sha1_hash values
will make this tricker.
Therefore, remove the value, and adjust the existing code to cope. This commit
also adds a new test which coveres some of the changed functionality.
|
|
|
|
| |
This to help test code which uses the (guix inferior) module.
|
|
|
|
|
| |
Using the test driver from build-aux/test-driver.scm, as this shows the test
errors when tests fail.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Previously, it was spliting versions up for the package pages. To stop this,
now it just matches the extensions it knows about (currently .html and .json).
|
|
|
|
| |
The first value should always be a list.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the routing layer handled the content negotiation, and the Accept
header was ignored. Now, the extension if one is provided in the URL is still
used, and more widely than before, but the Accept header is also taken in to
account.
This all now happens before the routing decisions are made, so the routing is
now pretty much extension independant (with the exception of the
/gnu/store/... routes).
|
|
|
|
|
| |
This adds more query parameter validation, and uses form-horizontal-control to
neaten up the view code.
|
| |
|
| |
|
| |
|
|
|
|
| |
Otherwise a URL like https://example.com? will cause this to fail.
|
| |
|
|
|
|
|
|
| |
Add handling for some query parameters to the branch page. This takes
advantage of the improvements for building forms and query parameter
validation.
|
|
|
|
| |
Each input is pretty complex, and this function helps handle that complexity.
|
|
|
|
| |
These are useful for constructing HTML ids and similar things.
|
|
|
|
|
|
|
|
|
| |
The query parameters feed in to the results shown, but also forms on
pages. Validation is important to avoid errors and security issues, but it's
also important to provide appropriate feedback to the user.
This module provides some utilities and structure around handling query
parameters.
|