Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: generate component name #323

Closed

Conversation

zhiyuanzmj
Copy link

@zhiyuanzmj zhiyuanzmj commented Oct 31, 2022

Description

fixes #322

Additional context

image


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following

  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

@zhiyuanzmj zhiyuanzmj reopened this Oct 31, 2022
@hannoeru
Copy link
Owner

hannoeru commented Nov 7, 2022

@zhiyuanzmj can we have a option to control this?

@zhiyuanzmj
Copy link
Author

@zhiyuanzmj can we have a option to control this?

Maybe I should create a new plugin to transform code, for this I need to export getPageRouteMap api.

@zhiyuanzmj
Copy link
Author

@zhiyuanzmj can we have a option to control this?

How about this pr #331 ?

@zhiyuanzmj
Copy link
Author

Or what option name should I call it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KeepAlive component's name which auto generated by route.name
2 participants