-
Notifications
You must be signed in to change notification settings - Fork 7
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
Added server autobot that crawls an index and build scenarios #50
Conversation
Added explorer file
Added feature field crawling Added stopwords
Added Parameters
added scenarioBuilder and configuration settings
Refactored Scenario input
Added bot to client
removed null in getInfos response
|
||
import ( | ||
"github.com/erocheleau/uabot/explorerlib" | ||
"github.com/erocheleau/uabot/scenariolib" |
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.
github.com/coveo/uabot/scenariolib
FROM golang | ||
|
||
#get source code | ||
RUN git clone https://github.com/adambbolduc/uabot.git |
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.
might want to change this ?
what do you think @erocheleau
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 are right !
Need to fix build before merge. |
Also you desperately need to comment the new stuff if you hope that one day I will be able to go through it :) I don't know what IDE you use to code but a go linter would ask you to comment ANYTHING that is exposed (any function, variable, struct, constant, etc. that starts with a capital letter) This is to also be able to generate stuff like this which is done automagically with go: |
No description provided.