-
Notifications
You must be signed in to change notification settings - Fork 315
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
Included StringIndexer and StringIndexerModel along with related test… #804
base: main
Are you sure you want to change the base?
Conversation
/// <param name="source"></param> | ||
/// <returns></returns> |
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.
Could you please add the param
and returns
description?
@ramanathanv Is this PR ready to review? I see some |
Hi @Niharikadutta , In the test case, I am trying to compare two List objects using Assert.Equal(). I notice in the test results that the Lists have the same content (see image below). Still there is an error. I assume that there must be a different way to compare the Lists. Can you please suggest me a way an alternate way to do this comparison? Thanks. |
I see "..." in the output. Can you compare elements one by one to see where the difference comes from? |
Hi @imback82 , |
What I meant was if you are comparing two lists, you can compare elements in those lists one by one instead of comparing them at the list level. Does it make sense? |
In StringIndexer there are a few calls which are missing the get* at the beginning - if I change them all to get* then the test passes for me.
should be
should be
should be
should be
If you change those then the tests should pass :) |
Thanks @GoEddie for identifying the issue . I have fixed the property names. But the test fails for unknown reasons. Can you please re-initiate the build/tests? |
Hi,
I am creating this pull request that implements the basic methods in StringIndexer and StringIndexerModel class along with Test cases.
This is related to "Implement ML Features" #381