If code changes were made then they have been tested.
I have updated the documentation to reflect the changes.
This PR fixes an issue.
This PR adds something new (e.g. new method or parameters).
This PR is a breaking change (e.g. methods or parameters removed/renamed)
This PR is not a code change (e.g. documentation, README, ...)
## Summary
## Checklist
<!-- Put an x inside [ ] to check it, like so: [x] -->
- [ ] If code changes were made then they have been tested.
- [ ] I have updated the documentation to reflect the changes.
- [ ] This PR fixes an issue.
- [x] This PR adds something new (e.g. new method or parameters).
- [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
- [ ] This PR is **not** a code change (e.g. documentation, README, ...)
Is this really needed? I remember seeing Danny and some other people in d.py talk about this - they agreed that since they're no easy way for users themselves to the Discord timestamp markdown, that it really wasn't worth it, and I kinda have to agree. There's no UI to make the timestamp, meaning most users would have to hear about this markdown from some source and then actually learn how to use it, which I'm willing to bet most users won't be able to do both.
I think it's best to let bot developers decide if it's worth making a converter like this for the small amount of Discord users that know how to use said markdown.
Is this really needed? I remember seeing Danny and some other people in d.py talk about this - they agreed that since they're no easy way for users themselves to the Discord timestamp markdown, that it really wasn't worth it, and I kinda have to agree. There's no UI to make the timestamp, meaning most users would have to hear about this markdown from some source and then actually learn how to use it, which I'm willing to bet most users won't be able to do both.
I think it's best to let bot developers decide if it's worth making a converter like this for the small amount of Discord users that know how to use said markdown.
I'm with astrea/Danny/others on this one, I don't see this as useful in the library. If discord added some sort of UI to create timestamps I could see a use case here. As it stands, I don't see this being used
I'm with astrea/Danny/others on this one, I don't see this as useful in the library. If discord added some sort of UI to create timestamps I could see a use case here. As it stands, I don't see this being used
I'll reiterate that as NC has suggested there is an incuded util, I think thats important for a user to be able to extract a datetime from a timemstamp. I can remove the converter however. Also having a converter doesn't hurt, but I think yeah users can implement the converters with the util.
I'll reiterate that as NC has suggested there is an incuded util, I think thats important for a user to be able to extract a datetime from a timemstamp. I can remove the converter however. Also having a converter doesn't hurt, but I think yeah users can implement the converters with the util.
Yeah, I can agree that the util itself makes sense - I can think of some uses a bot maker might have for it. Just think a converter doesn't make much sense at this time - it doesn't hurt, but I think it's best not to add unnecessary features if possible.
Yeah, I can agree that the util itself makes sense - I can think of some uses a bot maker might have for it. Just think a converter doesn't make much sense at this time - it doesn't *hurt*, but I think it's best not to add unnecessary features if possible.
This pull request has changes conflicting with the target branch.
discord/ext/commands/errors.py
discord/utils.py
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Checklist
Is this really needed? I remember seeing Danny and some other people in d.py talk about this - they agreed that since they're no easy way for users themselves to the Discord timestamp markdown, that it really wasn't worth it, and I kinda have to agree. There's no UI to make the timestamp, meaning most users would have to hear about this markdown from some source and then actually learn how to use it, which I'm willing to bet most users won't be able to do both.
I think it's best to let bot developers decide if it's worth making a converter like this for the small amount of Discord users that know how to use said markdown.
I'm with astrea/Danny/others on this one, I don't see this as useful in the library. If discord added some sort of UI to create timestamps I could see a use case here. As it stands, I don't see this being used
I'll reiterate that as NC has suggested there is an incuded util, I think thats important for a user to be able to extract a datetime from a timemstamp. I can remove the converter however. Also having a converter doesn't hurt, but I think yeah users can implement the converters with the util.
Yeah, I can agree that the util itself makes sense - I can think of some uses a bot maker might have for it. Just think a converter doesn't make much sense at this time - it doesn't hurt, but I think it's best not to add unnecessary features if possible.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.