Skip to content

fix: issue 4240 Calling resolve on catch block parameter throws exception #4279

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

Merged
merged 2 commits into from
Dec 30, 2023
Merged

Conversation

jlerbsc
Copy link
Collaborator

@jlerbsc jlerbsc commented Dec 30, 2023

Fixes #4240 .

Also fixes #3111 Unable to resolve Parameter in LambdaExpr due to NoSuchElementException

@jlerbsc jlerbsc merged commit 6d50915 into javaparser:master Dec 30, 2023
@jlerbsc jlerbsc added this to the next release milestone Dec 30, 2023
@jlerbsc jlerbsc added the PR: Fixed A PR that offers a fix or correction label Dec 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: Fixed A PR that offers a fix or correction
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Calling resolve on catch block parameter throws exception. Unable to resolve Parameter in LambdaExpr due to NoSuchElementException
1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy