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

Use emulator issues stream notification to initiate schema reload #7411

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

hlshen
Copy link
Contributor

@hlshen hlshen commented Jul 3, 2024

No description provided.

@hlshen hlshen requested a review from rosalyntan July 3, 2024 17:01
const issueMessage = `Data Connect Emulator: ${issue.kind.toString()} - ${issue.message}`;
if (issue.severity === Severity.ALERT) {
vscode.window.showErrorMessage(issueMessage);
} else if (issue.severity === Severity.NOTICE) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not blocking for this PR, but I wonder if we should chat to discuss if there should be a standard way for VSCode to handle different severity levels (i.e. would you prefer the FILE_RELOAD notification to be sent with DEBUG severity level, so you can keep displaying NOTICE as a warning message?)

) {
const obsErrors = await getEmulatorIssuesStream(configs, fdcEndpoint);
const obsConverter = {
next(nextResponse: EmulatorIssueResponse) {
if (nextResponse.result?.issues?.length) {
for (const issue of nextResponse.result.issues) {
displayAndHandleIssue(issue, isPostgresEnabled);
console.log("HAROLD: ", issue)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leftover log!

@joehan joehan merged commit 85d27c5 into master Jul 9, 2024
19 checks passed
@joehan joehan deleted the hlshen/reload-schema branch July 9, 2024 17:27
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.

None yet

3 participants