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

What is the recommanded workflow to update the docs as we go#94

Unanswered
jonatanzafar59 asked this question inQ&A
Discussion options

Hi guys, amazing app.
So after the first generation, I went through it and edited some inaccurate or misleading information.
Lets say I wanna re-generate the docs, I don't wanna go all over again and update it. is there a way for the app to take into account? or should I just let my cursor update it after the first draft?

You must be logged in to vote

Replies: 2 comments

Comment options

Currently there isn't support and asking cursor to update sounds reasonable. Let me know if that works well.

You must be logged in to vote
0 replies
Comment options

How can I generate documentation for all the files in a .NET Core project?
I've noticed that often the documentation doesn't include all methods and properties in the classes (.cs files).
Also, when the generation process breaks partway through, it restarts from the beginning next time instead of resuming from where it left off.
This causes it to use more tokens and makes it more costly.
how I can include the all-important class (.cs file) to generate the document?

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
3 participants
@jonatanzafar59@zachary62@ravichandrasingh

[8]ページ先頭

©2009-2025 Movatter.jp