8000 Portal v0.2 · Issue #299 · hookdeck/outpost · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Portal v0.2 #299

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

Open
5 tasks
leggetter opened this issue Mar 27, 2025 · 5 comments
Open
5 tasks

Portal v0.2 #299

leggetter opened this issue Mar 27, 2025 · 5 comments
Labels

Comments

@leggetter leggetter moved this from Backlog to Todo in Outpost Releases Apr 1, 2025
@alexluong
Copy link
Collaborator

Rethink pagination display since cursor based pagination doesn't allow for a sense of where you are when viewing a large list of items (e.g. Viewing 10 of 500, but which 10?)

@leggetter any idea here? I think one issue with this is that the event list may grow continuously, so we can't tell for sure where the current page may be. But also this is just a limitation of cursor-based pagination, so there's no way around it. Maybe we should have a different display instead of "Viewing 10 of 500"?

@alexluong
Copy link
Collaborator

Add Feature labels to destination type creation flow

How do we know what features each destination should have? Should this be part of the API, or more FE-only? I assume metadata in the API, just seems a tad irrelevant to the Outpost delivery mechanism itself and more UI focus.

@alexluong
Copy link
Collaborator

@leggetter can you clarify this as well?

Add links to destination type documentation within Create Flow (e.g. SQS, RabbitMQ, Hookdeck Event Gateway)

@leggetter
Copy link
Collaborator Author

@leggetter can you clarify this as well?

Add links to destination type documentation within Create Flow (e.g. SQS, RabbitMQ, Hookdeck Event Gateway)

Handled in #214

@leggetter
Copy link
Collaborator Author

Add Feature labels to destination type creation flow

How do we know what features each destination should have? Should this be part of the API, or more FE-only? I assume metadata in the API, just seems a tad irrelevant to the Outpost delivery mechanism itself and more UI focus.

Should be on the destination /destination-types/:type endpoint.

We'll define the features and which destination types have which features.

Moved this into #319

@leggetter leggetter moved this from Todo to Backlog in Outpost Releases Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

2 participants
0