Skip to content

[typscript] change @export to @exports#21754

Open
jckr wants to merge 2 commits intoOpenAPITools:masterfrom
jckr:fix_issue21753
Open

[typscript] change @export to @exports#21754
jckr wants to merge 2 commits intoOpenAPITools:masterfrom
jckr:fix_issue21753

Conversation

@jckr
Copy link
Copy Markdown

@jckr jckr commented Aug 14, 2025

one of the typescript templates uses a @export tag which is incorrect - the right form is @exports (see https://jsdoc.app/tags-exports). As a result, the generated code may trigger linters.

This PR corrects the syntax.

fixes #21753

@TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @topce @akehir @petejohansonxo @amakhrov @davidgamero @mkusaka @joscha

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@macjohnny
Copy link
Copy Markdown
Member

thanks!

@macjohnny
Copy link
Copy Markdown
Member

@jckr please re-generate the samples (see PR description)

@davidgamero
Copy link
Copy Markdown
Contributor

im debugging the same windows test failure too (unrelated to the samples afaict)

the grade Unknown command-line option '-b'. error

@jckr
Copy link
Copy Markdown
Author

jckr commented Aug 15, 2025

@macjohnny I have added a commit for the samples

@macjohnny
Copy link
Copy Markdown
Member

@jckr can you merge the most recent master? maybe that resolves the CI issues

@macjohnny
Copy link
Copy Markdown
Member

FYI this is superseded by #21776

@macjohnny
Copy link
Copy Markdown
Member

closing this in favor of #21776

@macjohnny macjohnny closed this Aug 20, 2025
@macjohnny macjohnny reopened this Aug 20, 2025
@macjohnny
Copy link
Copy Markdown
Member

oops, #21776 was for typescript-axios, while this one is for typescript, so reopened and waiting for merging in the latest master branch

@macjohnny
Copy link
Copy Markdown
Member

but it raises an interesting question: should the jsdoc be removed altogether, since the information is already present in typescript?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] [typescript] @export is not a valid jsdoc decorator

3 participants