Skip to content

NewXKitBot 2.0#4

Open
Wolvan wants to merge 8 commits intonew-xkit:masterfrom
Wolvan:rewrite_1
Open

NewXKitBot 2.0#4
Wolvan wants to merge 8 commits intonew-xkit:masterfrom
Wolvan:rewrite_1

Conversation

@Wolvan
Copy link
Member

@Wolvan Wolvan commented Nov 20, 2015

I decided to do a full rewrite of the bot, in turn cleaning it up and making it easier to use and to configure

README.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be misread as "(New-XKit Bot is the team behind New XKit)'s helping little assistant" rather than "New-XKit Bot is (the team behind New XKit)'s helping little assistant". For clarity, I would rewrite this as

New-XKit Bot is New XKit team's little assistant

@Wolvan Wolvan force-pushed the rewrite_1 branch 2 times, most recently from 3a06d01 to 3598bab Compare November 20, 2015 03:12
@Wolvan
Copy link
Member Author

Wolvan commented Nov 20, 2015

Made your changes top the README.md, @bvtsang

@Wolvan Wolvan added this to the 2.0.0 milestone Nov 20, 2015
README.md Outdated
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub's Markdown Basics document recommends using single backticks (`).

@0xazure
Copy link

0xazure commented Nov 20, 2015

The lack of in-line documentation makes things a little tricky to understand what's going on, particularly in the cases where RegEx is being used to transform the messages.

I would also still like to see thorough documentation as to how the NewXKit bot is set up and run on our infrastructure. It doesn't necessarily need to be a part of this project, but formal deployment instructions would be helpful.

Generally, having monolithic do-everything files make it more difficult to reason about a project. Splitting the code up by concerns and making things more modular would go a long way to help readability and understanding.

These have just been my initial thoughts and comments, and do not constitute a formal code review.

README.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we standardized on New XKit in prose and new-xkit in code, fyi.

@nightpool
Copy link
Member

would be nice to have this linted

@0xazure
Copy link

0xazure commented Nov 20, 2015

would be nice to have this linted

I'd probably recommend XO for a Just Works ™️ linter, if we don't want to fuss with config options, otherwise ESLint.

Since this is a rewrite from scratch, clear out everything and restore a
clean workspace
After clearing out the old code, re-init the repository with a proper
README.md, a LICENSE.md (GPL-2.0) and a .gitignore for NodeJS projects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants