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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: whitespace issue with CommentBlock introduced after new PR #15036
Comments
Hey @pyramation! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite. |
https://github.com/pyramation/babel-issue-15036 the breaking commit is when I upgrade babel: pyramation/babel-issue-15036@e298022 You can see leading comments lose their trailing newlines |
I've found a new one that is technically the same issue, but should we reopen this or make a new one? this /** This describes how the endpoint is implemented when the lease is deployed */
export enum Endpoint_Kind {
/** SHARED_HTTP - Describes an endpoint that becomes a Kubernetes Ingress */
SHARED_HTTP = 0,
/** RANDOM_PORT - Describes an endpoint that becomes a Kubernetes NodePort */
RANDOM_PORT = 1,
UNRECOGNIZED = -1,
} becomes /** This describes how the endpoint is implemented when the lease is deployed */
export enum Endpoint_Kind {
/** SHARED_HTTP - Describes an endpoint that becomes a Kubernetes Ingress */SHARED_HTTP = 0,
/** RANDOM_PORT - Describes an endpoint that becomes a Kubernetes NodePort */RANDOM_PORT = 1,
UNRECOGNIZED = -1,
} |
Either way looks fine to me. |
Thanks! I think re-open makes sense ;) |
馃捇
How are you using Babel?
Programmatic API (
babel.transform
,babel.parse
)Input code
generate code from this AST in the lastest version after this PR: #14979
Configuration file name
No response
Configuration
No response
Current and expected behavior
expected
current after PR
diff
Environment
System:
OS: macOS 12.2
Binaries:
Node: 16.14.0 - /usr/local/bin/node
Yarn: 1.18.0 - /usr/local/bin/yarn
npm: 8.3.1 - /usr/local/bin/npm
Monorepos:
Yarn Workspaces: 1.18.0
Lerna: 4.0.0
npmPackages:
@babel/cli: 7.19.3 => 7.19.3
@babel/core: 7.19.3 => 7.19.3
@babel/eslint-parser: ^7.19.1 => 7.19.1
babel-core: 7.0.0-bridge.0 => 7.0.0-bridge.0
babel-jest: ^29.1.2 => 29.1.2
eslint: 8.25.0 => 8.25.0
jest: 29.1.2 => 29.1.2
lerna: 4.0.0 => 4.0.0
Possible solution
No response
Additional context
#14979
The text was updated successfully, but these errors were encountered: