-
Notifications
You must be signed in to change notification settings - Fork 25
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
Extract selection option labels for Analytics #877
Conversation
@Rello Hi! Are you still working on this? |
Hi @juliushaertl you think we can merge this? |
I am afraid this has potential to be breaking potential existing API use cases. I suppose the IDs of the selection can be fetched already (did not double check). Not that the output is much documented. There is a conflict btw. If we merge, it's better to have the commits squashed. |
@blizzz what do you suggest? I think of skipping this and simply ship the datasources for everything with Analytics itself. Kind of double work because local duplication of the API logic might be required in many places. but not impacting other apps suggestion? |
as discussed with @blizzz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll make me extra happy by squashing the commits =)
P.S.: Let me do that quickly
return ['header' => $header, 'dimensions' => array_slice($header, 0, count($header) - 1), 'data' => $data, //'rawdata' => $data, | ||
'error' => 0,]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick-as-a-Service: indentation looks odd. Would be better in the previous style.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let me check which code styler setting messed this up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
saw to late. but a follow up pr is welcomed.
when column type selection is used, the datasource needs the labels, and not the internal ids Signed-off-by: Rello <Rello@users.noreply.github.com>
/backport to stable0.7 |
when column type selection is used, the API needs to deliver the labels, and not the internal ids
fixes Integration with NC Tables Rello/analytics#385
Using lib/Analytics (and not lib/Datasource) for better readability
Adopting from LegacyRow to Row