⚠️ No Changeset found

Latest commit: db0909e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

PR Summary

• Addition of setupDescriptionHandler in Vue Docgen API Package
  A new module called setupDescriptionHandler has been integrated into the Vue Docgen API package. This module will contribute to enhancing the functionality of the package.

• Test File for setupDescriptionHandler
  To ensure the proper functioning of the setupDescriptionHandler module, a new testing file has been introduced. This will allow developers to validate and verify the improvements introduced by this new module.

• Implementation File for setupDescriptionHandler
  The actual working code for the new setupDescriptionHandler module has been added. This file contains all the necessary instructions that make up this new functionality within the Vue Docgen API package.

Passing run #544 ↗︎

0

57

0

0

0

Details:

Review all test suite changes for PR #1621 ↗︎

I would prefer to use the following syntax to keep common matters together:

<script setup lang="ts">
import { ... } from "vue";
/**
 * My super description
 */
defineOptions({
  name: 'ComponentNameInDevTools'
})
...

This way, all features added to the options would be available in setup too.
Also, there would be no need for a handler specific to description.

What do you think?

Sure ! But I am confused: I used the @description tag because I could not know which comment block is the description, I had to filter out all the other comments. (I am not an expert into AST) How would you know which comments are for something else, and which are for description ?

And then, where to put the logic if not in a specific handler ? In the setupExposeHandler ?