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

Implement database query and view for showing latest API backends #687

Closed
5 of 6 tasks
bajiat opened this issue Dec 4, 2015 · 4 comments
Closed
5 of 6 tasks

Implement database query and view for showing latest API backends #687

bajiat opened this issue Dec 4, 2015 · 4 comments
Assignees

Comments

@bajiat
Copy link
Contributor

bajiat commented Dec 4, 2015

As a part of the front-page re-design we need a view of the newest additions to API catalog. This requires both a query (publication and subscription) and a view.

  • Create publication
  • Create subscription
  • Create temporary route (For testing purposes, until home page is redesigned)
  • Create template
  • Use specific query that contains sorting by created_at field & limit amount of returned documents, for example to 6.
  • Integrate latestApiBackends template to a redesigned home page.
@frenchbread
Copy link
Contributor

Interested in this one.

@brylie brylie added planning and removed APIKA labels Dec 16, 2015
@bajiat
Copy link
Contributor Author

bajiat commented Dec 21, 2015

@frenchbread Are you still interested? Might require a schema update so that we have a creation date for API backends.

@frenchbread frenchbread self-assigned this Dec 22, 2015
@frenchbread
Copy link
Contributor

Self-assigned.

Creation timestamp field for API backends should be already present in a schema.

@bajiat bajiat added this to the Sprint 19 milestone Dec 22, 2015
@bajiat bajiat added ready and removed planning labels Dec 22, 2015
@frenchbread
Copy link
Contributor

Created a PR #727 with WIP label.

The reason for WIP label is that since we do not have a redesigned version of a home page yet, there is no actual place where to put latestApiBackends template. For that reason I've added a temporary route /latest for testing.

Does it make sense to keep the PR in WIP until the new design is submitted? Or we can merge it now and do related integrations later?

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

No branches or pull requests

4 participants