You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the paper, the smell is described as follows:
Problem
If the columns are not selected explicitly, it is not easy for developers to know what to expect in the downstream data schema. If the datatype is not set explicitly, it may silently continue the next step even though the input is unexpected, which may cause errors later. The same applies to other data importing scenarios.
Solution
It is recommended to set the columns and DataType explicitly in data processing.
Since this function is too flexible, it is hard to know what the column types for the developers want. Thanks for the recommendation though, as it is a real concern.
Hello!
I found an AI-Specific Code smell in your project.
The smell is called: Columns and DataType Not Explicitly Set
You can find more information about it in this paper: https://dl.acm.org/doi/abs/10.1145/3522664.3528620.
According to the paper, the smell is described as follows:
Example:
You can find the code related to this smell in this link:
PyShortTextCategorization/shorttext/data/data_retrieval.py
Lines 123 to 143 in 1d1a67a
I also found instances of this smell in other files, such as:
File: https://github.com/stephenhky/PyShortTextCategorization/blob/master/shorttext/classifiers/embed/nnlib/VarNNEmbedVecClassification.py#L238-L248 Line: 243
.
I hope this information is helpful!
The text was updated successfully, but these errors were encountered: