-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
fix: Fix linter issues #397
Conversation
packages/core/src/parsing.ts
Outdated
@@ -65,7 +65,7 @@ export function parseJsonArrayFromText(text: string) { | |||
if (jsonBlockMatch) { | |||
try { | |||
jsonData = JSON.parse(jsonBlockMatch[1]); | |||
} catch (e) { | |||
} catch { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we log the error with console.error instead of removing this?
packages/core/src/parsing.ts
Outdated
@@ -118,7 +118,7 @@ export function parseJSONObjectFromText( | |||
if (objectMatch) { | |||
try { | |||
jsonData = JSON.parse(objectMatch[0]); | |||
} catch (e) { | |||
} catch { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here and everywhere else
LGTM outside of adding console.error for the catch statements |
@monilpat @martincik We have a build error, can we address before merge?
|
7cc6f58
to
d49611b
Compare
@jkbrooks Build and lint fixed. |
Relates to:
No specific issue linked - appears to be a code quality improvement PR
Risks
Low - Changes are purely related to code style and import organization with no functional changes.
Background
What does this PR do?
This PR addresses linting issues in the codebase by:
What kind of change is this?
Improvements (misc. changes to existing features)
Documentation changes needed?
My changes do not require a change to the project documentation.
Testing
Where should a reviewer start?
Review the changes in the following files:
Detailed testing steps
No, automated tests are fine. These changes are purely syntactic and don't affect functionality.
The changes include:
Since these are linter-driven changes, existing tests should cover functionality verification.