-
Notifications
You must be signed in to change notification settings - Fork 248
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
fix: some bug fix related to tag and data element #1199
Conversation
for row in associations: | ||
data_element["type"] = row.type.value | ||
data_element[row.property_name] = ( | ||
row.data_element.to_dict() if row.data_element else row.primitive_type |
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.
don't serialize it here. Let it be serialized automatically when returning
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.
api json encoder wont do automatic serialization for nested objects.
}) => { | ||
const { data: tableColumnStats } = useResource( |
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.
since we don't get tags, data elements, and stats individually anymore, can you remove the api and resource?
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.
actually there are 3 /column/stats
apis, two of them are also not used today. should we remove all of them?
@register("/column/stats/<int:column_id>/", methods=["GET"])
@register("/column/stats/<metastore_name>/", methods=["POST"])
@register("/column/stats/", methods=["POST"])
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.
oh yeah lets remove all of them then
@@ -116,6 +119,9 @@ export interface IDataColumn { | |||
name: string; | |||
table_id: number; | |||
type: string; | |||
stats?: ITableColumnStats[]; |
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.
instead of stats?, can you separate the type out to be IDetailedDataColumn extends IDataColumn?
* fix: some tag ui bugs * comments * remove column stats api
* fix: some tag ui bugs * comments * remove column stats api
some bug fixes
Also removed the expand/collapse toggle button and move the column name before the column type