adds new conduit methods for countdown.edit and countdown.search
Details
- Reviewers
epriestley - Maniphest Tasks
- T12524: Modernize Countdown
- Commits
- rPd902d2ac6b39: Implement countdown.search and countdown.edit
Search:
Edit:
Diff Detail
- Repository
- rP Phabricator
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
src/applications/countdown/storage/PhabricatorCountdown.php | ||
---|---|---|
175 | Add a specification for epoch here too (for now, this is only used to generate documentation). | |
181 | For remarkup fields like this, I started doing something to try to future-proof them recently in D17603:
See also discussion in T12461. But the idea is that we might eventually want to be able to return text/html for these fields, or store other flavors of markdown, and we can do that without breaking the API if we emit a dictionary. So the output is currently: "description": "asdf" ...but for consistency with the new scheme in D17603, should be: "description": { "raw": "asdf" } | |
182 | Put an (int) cast on this so it emits into JSON as a number instead of a string (PHP is all loosey-goosey about this stuff and we currently don't try to enforce types when they come out of the database). That is, the output currently shows: "epoch": "19831981098" ...but better is: "epoch": 19831981098 ...so that languages which care more will have an easier time interacting with the API. |
src/applications/countdown/storage/PhabricatorCountdown.php | ||
---|---|---|
175 | Should the type be int or integer? |
src/applications/countdown/storage/PhabricatorCountdown.php | ||
---|---|---|
175 | I think I've been using 'epoch' -- it's purely documentation for humans for now so it's kind of made up. |