aboutsummaryrefslogtreecommitdiffstats
path: root/rust
Commit message (Collapse)AuthorAgeFilesLines
...
* more edit edgecases; editgroup status checkBryan Newbold2018-12-213-1/+22
|
* more state/edit edge case testsBryan Newbold2018-12-212-5/+63
|
* GET methods not in transactionsBryan Newbold2018-12-201-15/+15
|
* ident table redirect lookupsBryan Newbold2018-12-201-0/+5
|
* fix order of entity updateBryan Newbold2018-12-201-17/+20
|
* disallow self-redirectsBryan Newbold2018-12-201-4/+13
|
* enforce no-recursive-redirectsBryan Newbold2018-12-201-12/+39
|
* allow deletion of redirect-to-deletionBryan Newbold2018-12-202-2/+3
|
* many redirect implementationsBryan Newbold2018-12-145-38/+272
| | | | | | | | | | | | | | | | | | Probably should have split this commit up, it's huge: - accept the state of "redirect to a deletion", where redirect_id is Some but rev_id is None. call this a "redirect"; previously this was an invalid state. - GET for a deleted entity returns a 200 and a stub entity, not a 404 - to PUT a redirect, or to "revert" an entity to point at a specific pre-existing revision, PUT a stub entity. things are getting messy here... to detect this state, ensure the 'state' field is blank/none (this is for API usage ergonomics, where results from a GET are often re-used in a PUT or even POST) - rustfmt - maybe even more small tweaks along the way? mystery meat! Tests are in python, not rust (and a future commit)
* better return status for some error conditionsBryan Newbold2018-12-143-13/+31
|
* lookups implBryan Newbold2018-12-144-35/+240
|
* rust codegenBryan Newbold2018-12-1410-65/+248
|
* new rustfmt (1.31)Bryan Newbold2018-12-146-77/+127
|
* skeleton out new schema featuresBryan Newbold2018-12-135-75/+493
|
* schema tweaks, and rust codegenBryan Newbold2018-12-1310-142/+6057
|
* rustfmtBryan Newbold2018-12-131-1/+5
|
* implement hide flagBryan Newbold2018-11-267-110/+242
|
* codegen hide changesBryan Newbold2018-11-268-126/+422
|
* update TODOsBryan Newbold2018-11-141-0/+1
|
* add (disabled) test that invalid fields should errorBryan Newbold2018-11-141-0/+16
|
* implement new controlled vocabulariesBryan Newbold2018-11-143-16/+49
|
* enforce some controlled vocabularies in APIBryan Newbold2018-11-144-0/+128
|
* disable breaking CI testBryan Newbold2018-11-142-3/+6
| | | | | See commit comment for details; a problem with gitlab CI and setup() function, not the test in particular. Grump.
* fix date/datetime confusion on rust/API sideBryan Newbold2018-11-144-6/+72
| | | | | | Should have dug in to this earlier; python code was getting confused. This is a breaking API change, from a practical standpoint, as both python and rust code had been hacked to work around this.
* rustfmtBryan Newbold2018-11-144-59/+105
|
* try slowing down rust tests to fix socket collisionBryan Newbold2018-11-131-0/+3
|
* remove neadless second basic api client testBryan Newbold2018-11-131-10/+0
|
* bump rust and postgres versionsBryan Newbold2018-11-131-2/+2
|
* another old python test (doesn't merge)Bryan Newbold2018-11-131-0/+83
|
* start porting old python testsBryan Newbold2018-11-131-0/+148
|
* fiddle with test helper functionsBryan Newbold2018-11-133-145/+180
|
* start using client in some testsBryan Newbold2018-11-133-0/+69
|
* set default host in swagger spec to api.fatcat.wikiBryan Newbold2018-11-134-3/+4
|
* update codegen (trivial)Bryan Newbold2018-11-123-116/+115
|
* pv in line mode during exportsBryan Newbold2018-10-121-1/+1
|
* better default file namesBryan Newbold2018-09-251-1/+1
|
* fix isbn13 size check (!)Bryan Newbold2018-09-221-2/+2
|
* update export commandBryan Newbold2018-09-221-1/+1
|
* rustfmt, and implement schema tweaksBryan Newbold2018-09-226-105/+75
|
* container_name (not title), and shrink some BIGINTsBryan Newbold2018-09-221-4/+4
|
* codegen fatcat-api-specBryan Newbold2018-09-2210-2809/+2979
|
* squelch diesel macro warningsBryan Newbold2018-09-182-0/+4
|
* fatcat-export rustfmtBryan Newbold2018-09-171-28/+50
|
* re-generate database_schema.rsBryan Newbold2018-09-171-23/+23
|
* fix CHECK clausesBryan Newbold2018-09-173-22/+23
|
* UNIQUE constraint on edits (ident per editgroup)Bryan Newbold2018-09-171-15/+10
|
* use timestamptz (not WITHOUT TIME ZONE)Bryan Newbold2018-09-171-8/+10
|
* CHAR/VARCHAR -> TEXT w/ CHECKBryan Newbold2018-09-171-15/+28
|
* remove is_not_null redundant lookup conditionsBryan Newbold2018-09-151-12/+0
|
* update extid columns: varchar size limits, no char columnsBryan Newbold2018-09-151-15/+15
| | | | | | | | | | | | In PostgreSQL, there is no query or size differences between CHAR, VARCHAR, and TEXT: they use the same backend. CHAR will pad out with spaces and VARCHAR enforces a size limit. The enforced VARCHAR size limit seems like ok defensive programming/schema here, preventing large values from getting stored for some columns. I have some FUD concern about fixed-sized identifiers and indexes, so switching old CHARs (eg, sha1 hex encoded columns) to VARCHAR instead.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-24 23:17:15 +0000