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
Introduce an Endpoint API #6280
Comments
WIP PR: #6283 |
This was referenced Jan 8, 2018
DrewAPicture
added a commit
that referenced
this issue
Jan 9, 2018
DrewAPicture
added a commit
that referenced
this issue
Jan 9, 2018
…eraging get_items_sorted() from #6280.
Merged #6283 🎉 |
🎉!
…On Sat, Jan 13, 2018 at 9:47 AM, Drew Jaynes ***@***.***> wrote:
Merged #6283
<#6283>
🎉
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6280 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_HfZ3KN3-pVIJxXLieOc5n-xWByP4tks5tJ8GpgaJpZM4RU_ht>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#6254Background
Endpoints will represent any data-based container to be consumed by reports tab. They will take the form of a variety of view types: tile, table, chart, graph, or any other form of visual representation of data. The endpoint object will dictate which view types are supported and supply callbacks for retrieving and displaying data in the expected format.
Endpoints will be registered (like report tabs) with structured data and rendered using an instantiated
Endpoint
object. The view type dictates what form the ultimate object will take. It will also need to be possible for endpoints to be instantiated on the fly during report object creation.The text was updated successfully, but these errors were encountered: