Nextjs github repo bot closed documentation issue with wrong reason

[gmoniava]

Summary

I opened a documentation related issue: #75494 by following the template
but the bot closed it automatically with a wrong reason.
Reason: "To be able to investigate, we need access to a reproduction to identify what triggered the issue.".
But documentation issues need not have reproduction links.
I don't know where is the right place to report this problem so I am posting here.
Can someone help?

Additional information

No response

Example

No response

[icyJoseph]

I am not sure why it got closed like that, perhaps, you misclicked a checkbox?

Anyway, to answer the question. The Next.js docs are but one source, and while, they were one of the first places that Server Actions were introduced, since these are React features, it is expected that most detailed documentation on their usage is to be found over the React docs, while the Next.js still keep some kind of general overview.

There used to a React Fundamentals section, now gone, in the docs, because Next.js is a means to use React, but the React core belongs to the React team.

To answer the question, transitions, are built-in to the concurrent rendering behavior, which means that, when you wrap some kind of state transition, or React work, React can make sure to show Suspense boundaries, give you access to whether or not the transition has been committed, and even use optimistic state updates.

call the Server Function in a Transition, which allows you to display a loading indicator, show optimistic state updates, and handle unexpected errors.

• Loading indicator, with isPending from useTransition, see, https://react.dev/reference/react/useTransition#preventing-unwanted-loading-indicators and https://react.dev/reference/react/useTransition#building-a-suspense-enabled-router
• For use with useOptimistic, https://reetesh.in/blog/react-useoptimistic-and-usetransition-hooks-explained, though it is outside the React docs...

[gmoniava]

I am not sure why it got closed like that, perhaps, you misclicked a checkbox?

I don't remember any check box you can even tell from the structure of my github issue that a documentation issue template was used to create it.

Anyway I know I need to use the transitions for server functions (at least react docs suggest so), but my goal was to highlight that Nextjs currently has misleading information - at least it is inconsistent with react docs. And I opened that issue with goal that those get fixed because it will confuse people; and in the way I discovered that even the Nextjs bot is working incorrectly and closing my documentation issues.

So if anyone here can help me bring this information to relevant people from Nextjs that would be nice.

[icyJoseph]

Well, what about this, https://react.dev/reference/rsc/server-functions:

I think the root issue is that( in it has been like this since the react@canary was introduced to next.js) a lot of this technology is still maturing and developing, surely, they claim it is production ready, but documentation, testing helpers, and even terminology keeps growing.

So now we have Server Functions, from the React core docs, which have also always shown both, calling the function without a transition, and without. However now they make a precision, or hint, at a wider concept the Server Function, and a more specific concept, Server Action, yet their docs show the onClick still being used.

I think, calling it misleading information, is far too harsh here, nor is it inconsistent as the screenshot and link shown, it is just a general, valid I think, critic to all of this, and it is that, a whole bunch of supporting stuff, is not there 100% yet.

[gmoniava]

Somehow I overlooked that, indeed now it seems react docs has conflicting information, one showing without transition (your example) and one with (the way it is written here makes you think you should always use transition). This is confusing...I would open an issue on this but often it gets ignored.

Ps. For example recently they changed (after I commented on gh) useActionState docs too stating if you want to call action returned by it outside forms, you need to wrap it in transition.