Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Documentation struggles#9839

mmontag started this conversation inGeneral
May 8, 2023· 3 comments· 3 replies
Discussion options

Which application is this bug report for?

Documentation

Issue description

Hi all, new to discord.js and really like it so far. However, I'm struggling with the discord.js documentation.
Two things in particular:

Steps to Reproduce

none

Versions

none

Issue priority

Low (slightly annoying)

You must be logged in to vote

Replies: 3 comments 3 replies

Comment options

Noted.

  1. This is intended. It is the "old" or legacy version of discord.js. It doesn't mean that its outdated or anything, it's still the latest version as of right now.
  2. The documentation you are on is an API reference, as others call it. It is automatically generated. It is not meant to work as a guide or have searchable articles that show you how to "use" stuff. That is what the guide is for:https://discordjs.guide/
You must be logged in to vote
0 replies
Comment options

+1, the documentation is really confusing—I'm still unclear; is it recommended we use@discordjs/core ordiscordjs? 🤔 🤯

You must be logged in to vote
1 reply
@tipakA
Comment options

/core is a subpackage that doesn't have all the "hand holding" you get withdiscord.js. If you know what you're doing, or know why would you want to, you're probably good to go with/core, otherwisediscord.js is most likely the one you should use.

That said, theold. subdomain is overall confusing. The reason that's done this way is because the new docs only work with TypeScript code, and discord.js itself is the only thing that is still in JavaScript. The reasoning shouldn't really be "old version of d.js" but "old version of docs", because thereisn't a newer version of discord.js (guide has av13 subdomain for "legacy" content if you need it, but the main address displays current content).

When The Eventual TypeScript Rewrite™️ of discord.js will happen, it will be on the new docs as discord.js just fine, alongside all the other subpackages.

Comment options

The documentation is really worse than ever, but there's this version who at least tries to be as good as it used to be

Well there was I link here that I just searched fast and wrong pasted, I can't find the good docs anymore ToT

You must be logged in to vote
2 replies
@Qjuh
Comment options

QjuhDec 19, 2023
Collaborator

We‘re always happy about feedback. What parts of the new docs do you deemworse than ever and how are the old docs better in that aspect?

@alaanvv
Comment options

Well, I'll ignore the fact I loved that old style.

Maybe for you the points I'm going to say are all refutable, but know that I'm just an average user with 2IQ

Besides the style, the search system doesn't seem to be straight, it feels like sometimes I'm typing an exact thing and that isn't the first item of the results
2. The navbar also seems to be with too much (I know it's supposed to have everything, but maybe there's a solution for this)

That's what I can notice, but it clearly feels slower than the old one

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
6 participants
@mmontag@danielgwilson@iCrawl@tipakA@Qjuh@alaanvv
Converted from issue

This discussion was converted from issue #9554 on September 17, 2023 09:54.


[8]ページ先頭

©2009-2025 Movatter.jp