Addition of end command and greetings.py

[chraem]

End Command in utils.py

• Allows the termination of the bot in a shorter time. This will help developers that run their programs without IDE.

Test.py

• This is a test file.
• Provides a basic how-to of text embeddings and mentioning a user (currently the author of the message).

[huenique]

Almost there, just need to go over the syntax/code guideline. It's kinda important that we identify and resolve any syntax and style issues. Could you run black and isort against the dayong directory, like so

black dayong

isort --profile black dayong

Then try running flake8 and pylint

flake8 dayong

pylint dayong

[chraem]

Will do that, thanks.

[huenique]

if there are issues, changes should be made and committed. something like "refactor: enforce code style" should be enough. thanks

[chraem]

• Done running my code in black, isort, flake8, and pylint; it went smoothly but still have this syntax suggestion by pylint:

  dayong\bot.py:108:8: E0237: Assigning to attribute 'members' not defined in class slots (assigning-non-slot)

• Fixed the issue with embedding emojis.

• Added the actual greeting feature, greetings.py

• Already test the .end command. The .end command is not visible to non-owners, even they typed .help.

[huenique]

The changes in the README file aren't quite right.

5. Run poetry shell. This will create a virtual environment and finds the pyproject.toml in the current directory.

6. Run poetry install. This will install all the dependencies listed in poetry.lock.

Number 5 doesn't make sense here. When poetry is run with the shell argument, it first finds the pyproject.toml file and creates the virtual environment based on that. However, if a virtual environment already exists for said file, it only needs to start it.

Number 6 is missing a few details but I don't suggest adding them. The pyproject.toml file designates the dayong directory as a package (name = "dayong"), hence everything inside it will be installed in the dist-packages or site-packages when poetry install is run. For the package dependencies, poetry installs everything in the poetry.lock file, but if that file doesn't exist, it uses pyproject.toml and then generates poetry.lock.

For now, I think it's best to revert the changes made to the README. Since it seems opinionated, I'd like to add my two cents. I prefer keeping it short and simple. Moreover, it's really not necessary for the reader to immediately know how poetry works as it isn't totally related. If they are interested, poetry's repository is already linked.

[huenique]

only remaining issue is with the readme file, everything else looks good. will merge once resolved 🙏

[chraem]

I've already edited the README, thanks for your correction 😊

[huenique]

really well done ✨