- 09 6月, 2021 5 次提交
-
-
由 Joe Previte 提交于
There was a case with the hashed-password which had multiple equal signs in the value and it wasn't being parsed correctly. This uses a new function and adds a few tests.
-
由 Joe Previte 提交于
-
由 Joe Previte 提交于
-
由 Joe Previte 提交于
Since this checks if they are authenticated using the hash/password and it's async, we need to update authenticated to be async, which means we have to update it everywhere it's used.
-
由 Joe Previte 提交于
-
- 10 2月, 2021 1 次提交
-
-
由 Asher 提交于
This way tests that import the http utilities but not the routes won't error due to missing types.
-
- 19 12月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
Capital letters in the CLI are evil. cc @code-asher
-
- 09 12月, 2020 1 次提交
-
-
由 SPGoding 提交于
Resolve #2225.
-
- 11 11月, 2020 1 次提交
-
-
由 Asher 提交于
Also add a check that the domain has a dot. This covers the localhost case as well, so remove that.
-
- 06 11月, 2020 2 次提交
- 05 11月, 2020 2 次提交
- 04 11月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 31 10月, 2020 1 次提交
-
-
由 Asher 提交于
This will buffer any data sent to it until something is ready to listen on it.
-
- 27 10月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 21 10月, 2020 2 次提交
- 10 10月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
See https://stackoverflow.com/a/34881585/4283659 Closes #1538
-
- 01 10月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1582.
-
- 15 9月, 2020 1 次提交
-
-
由 Asher 提交于
Closes #1886.
-
- 31 8月, 2020 1 次提交
-
-
由 Jacob Goldman 提交于
-
- 14 8月, 2020 1 次提交
-
-
由 Asher 提交于
To help debug login issues.
-
- 09 8月, 2020 1 次提交
-
-
由 G r e y 提交于
Adds a str param to common/util::plural for pluralizing a string. Applies plural to entry.ts.
-
- 01 8月, 2020 2 次提交
- 31 7月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 30 7月, 2020 3 次提交
- 28 7月, 2020 1 次提交
-
-
由 Asher 提交于
A provider can now be registered on multiple endpoints (or potentially moved if needed).
-
- 13 5月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
-
- 18 4月, 2020 1 次提交
-
-
由 Asher 提交于
See #1532 for more context. - Errored JSON requests will get back the error in JSON instead of using the status text. This seems better to me because it seems more correct to utilize the response body over hijacking the status text. The caller is expecting JSON anyway. Worst of all I never actually set the status text like I thought I did so it wasn't working to begin with. - Allow the update error to propagate for JSON update requests. It was caught to show the error inline instead of an error page when using the update page but for JSON requests it meant there was no error and no error code so it looked like it succeeded. - Make errors for failed requests to GitHub less incomprehensible. Previously they would just be the code which is no context at all.
-
- 14 4月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1507.
-
- 09 4月, 2020 1 次提交
-
-
由 Asher 提交于
Otherwise the request will just hang.
-
- 03 4月, 2020 5 次提交