Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Including timezones API in configuration endpoint #6525

Merged
merged 1 commit into from Feb 24, 2016

Conversation

aileen
Copy link
Member

@aileen aileen commented Feb 17, 2016

Including timezones API in configuration endpoint

issue #6406

  • endpoint configuration/timezones refers to timezones.json file in data
  • added route for endpoint in api.js to use method read in configuration.js

@aileen
Copy link
Member Author

aileen commented Feb 17, 2016

#6421

ErisDS added a commit to ErisDS/Ghost that referenced this pull request Feb 19, 2016
refs TryGhost#6421, TryGhost#6525

- The configuration API endpoint was a bit of an animal:
   - It's used currently in two ways, once for general config, another for the about page.
   - These two things are different, and would require different permissions in future.
   - There was also both a browse and a read version, even though only browse was used.
   - The response from the browse was being artificially turned into many objects, when its really just one with multiple keys
- The new version treats each type of config as a different single object with several keys
- The new version therefore only has a 'read' request
- A basic read request with no key will return basic config that any client would need
- A read request with the about key returns the about config
- A read request with a different key could therefore return some other config
@aileen
Copy link
Member Author

aileen commented Feb 23, 2016

I changed the route for configuration/timezone regarding the changes from PR #6548.
The configuration/timezone endpoint will now read the timezones only and resolves in .json file like
{ configuration: [ { timezones: [array of timezones] } }
The configuration endpoint itself doesn't include the timezones anymore.

@aileen aileen changed the title [WIP] Including the timezones API in configuration endpoint Including timezones API in configuration endpoint Feb 24, 2016
refs TryGhost#6406
- endpoint configuration/timezones refers to timezones.json file in data
- added route for endpoint in api.js to use method read in configuration.js
sebgie added a commit that referenced this pull request Feb 24, 2016
Including timezones API in configuration endpoint
@sebgie sebgie merged commit ba96847 into TryGhost:master Feb 24, 2016
@ErisDS
Copy link
Member

ErisDS commented Feb 24, 2016

👍 🎉

@aileen aileen deleted the timezones_api branch June 28, 2016 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants