January 2021 Update

[Pythonic-Rainbow]

+ Added ro.py in libs.yml
+ Many embed that displayed a member's name/discriminator/id now directly mentions the member.
* Code refactor and clean up.
+ Redesign ?libs

moderation.py

A large amount of code has been extracted to 2 methods.

* Fixed a bug which Moderators with no Library Developer role can't invoke moderation commands
^ Many commands now work.

I didn't test ?reason ?duration as I didn't have the database on my working dir.

[Pythonic-Rainbow]

Please note that for this to work, Member intent has to be enabled on Discord DevPortal as demonstrated in #developer_spot.

[Pythonic-Rainbow]

Also, @jmk-developer suggested that we might want to redesign the layout of ?libs as he thinks its too messy.

My current proposal is a layout like this

**Python**
[ro.py](their repo link): By jmkdev (jmkdev#0001) and iranathan(iranathan#5611)

...
**Java**
~~[Javablox](repo link): By Pythonic_Rainbow (Rainbow Breathing#7219)~~

where libs with a strike means dead libs.

I am thinking, should we keep those dead libs in libs.yml?

In the future, we might just migrate the list in libs.yml into the database, which should allow us to update the table by typing commands.

[sbhadr]

Please note that for this to work, Member intent has to be enabled on Discord DevPortal as demonstrated in #developer_spot.

Has been enabled.

Also, @jmk-developer suggested that we might want to redesign the layout of ?libs as he thinks its too messy.

My current proposal is a layout like this

**Python**
[ro.py](their repo link): By jmkdev (jmkdev#0001) and iranathan(iranathan#5611)

...
**Java**
~~[Javablox](repo link): By Pythonic_Rainbow (Rainbow Breathing#7219)~~

where libs with a strike means dead libs.

I am thinking, should we keep those dead libs in libs.yml?

In the future, we might just migrate the list in libs.yml into the database, which should allow us to update the table by typing commands.

I do think that it needs a redesign but, striking out libraries as opposed to not having them in the list takes up a lot of unneeded space for seemingly no reason. I think the best course of action would be a command like:

?libs <language> where it returns all of the channels and links in the under the python_channelname abbreviation. Not only would it be more versatile but, we wouldn't have to update the list manually as much as compared to having a mod create the actual channel. A yml file is much more simplistic / stylistic than a json file would be (what we used previously iirc) and I really do not want to go back to using a json file. I'm more-so looking for automated & less manual stuff so that it's easier to integrate and the reliance on restarting the bot entirely to pull latest changes can be dropped especially with static files that could be dynamic such as the yml. Some commands however, deserve to be static so, in that sole case, it's fine. Lmk what you think. Thanks for the pull request & maintenance of this.

[Pythonic-Rainbow]

If I want to create a new python file, is there anything need to change on generate.py?

The new code heavily relies on moderation.xxx_embed() functions. Might want to create a new class for it.

[Pythonic-Rainbow]

Also can we create a ERROR_LOG_CHANNEL in .env?
Seems to ease development cuz i have to keep changing the channel ID

[Pythonic-Rainbow]

Code refactor is completed. Now it's just the matter of whether to update this or not.

?libs <language> where it returns all of the channels and links in the under the python_channelname abbreviation.

Can you give me a demo response in Markdown?

[sbhadr]

If I want to create a new python file, is there anything need to change on generate.py?

The new code heavily relies on moderation.xxx_embed() functions. Might want to create a new class for it.

Generates static files. If you have a static file that needs to be generated on restart (i.e re-cached) then, it makes sense to add it here. Otherwise, the file will not update. https://github.com/RbxAPI/Docs-Bot/blob/rewrite/generate.py#L57

Also can we create a ERROR_LOG_CHANNEL in .env?
Seems to ease development cuz i have to keep changing the channel ID

Probably a good idea.

Can you give me a demo response in Markdown?

Sure.

Karen: ?libs python
Docs:

Python
Library A - Author, link, channel
Library B - Author, link, channel
Library C - Author, link, channel

Karen: ?libs js
Docs:

Javascript
Library A - Author, link, channel
Library B - Author, link, channel
Library C - Author, link, channel

Something like this that is simple but, gets the job done.

[Pythonic-Rainbow]

So we are purging dead libs?

[jmkd3v]

I hope so 😞

[Pythonic-Rainbow]

How does this look like

[tacheometry]

I think it should only mention the channel name in the field value and only have the repo link & name as the title of each field

[sbhadr]

So we are purging dead libs?

Correct.

How does this look like

I think that the linked author name is a bit redundant. I think it should just be renamed to source or repo.

I think it should only mention the channel name in the field value and only have the repo link & name as the title of each field

Provide a visual representation as to what this means.

[tacheometry]

Provide a visual representation as to what this means.

Just realized, you can't set links as titles.

[Pythonic-Rainbow]

I think that the linked author name is a bit redundant. I think it should just be renamed to source or repo.

btw iirc we linked a dev's GitHub profile because some might not be in our server

[Pythonic-Rainbow]

Supports multi-author. This should be the final format. @jmkd3v

[jmkd3v]

Okay, looks great! Glad we can both get credit for our work. Excited to see this implemented soon!

[Pythonic-Rainbow]

Right. Everything is set besides the above "rename EmbedFactory" thing

[Pythonic-Rainbow]

Wat why is there conflicting files

[jmkd3v]

Sanjay seems to have modified main.py which you also modified?

[Pythonic-Rainbow]

Sanjay seems to have modified main.py which you also modified?

yep just realised he pushed something

[Pythonic-Rainbow]

Resolved file conflicts.

[sbhadr]

Completing some internal things to make this PR easier to put into life. Will be a bit.

[jmkd3v]

Any update on when this will be pushed to main?

[sbhadr]

Couple days. I'm trying to fix / improve some core stuff before I push this in.

[sbhadr]

Looks good on my end. Thanks for the PR. Merging.