Skip to content

Conversation

brandon-pereira
Copy link
Contributor

If I try to create a multi-line where statement in the UI, it does not persist the new line character, which leads to errors as well.

Fixes HDX-2527

@brandon-pereira brandon-pereira requested review from a team and SpencerTorres and removed request for a team September 30, 2025 19:24
Copy link

changeset-bot bot commented Sep 30, 2025

🦋 Changeset detected

Latest commit: cedcefa

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@hyperdx/app Patch
@hyperdx/api Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Sep 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
hyperdx-v2-oss-app Ready Ready Preview Comment Oct 6, 2025 3:19pm

Copy link
Contributor

github-actions bot commented Sep 30, 2025

E2E Test Results

All tests passed • 25 passed • 3 skipped • 204s

Status Count
✅ Passed 25
❌ Failed 0
⚠️ Flaky 0
⏭️ Skipped 3

View full report →

Copy link
Contributor

@MikeShi42 MikeShi42 left a comment

Choose a reason for hiding this comment

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

Is there a way we can still persist them? maybe %0A if needed?

I also saw that this fix unfortunately does not fix the dashboards filters case (sorry did not mention that in the original ticket!)

@brandon-pereira
Copy link
Contributor Author

Is there a way we can still persist them? maybe %0A if needed?

I also saw that this fix unfortunately does not fix the dashboards filters case (sorry did not mention that in the original ticket!)

@MikeShi42 that makes sense! I've changed the implementation and fixed the other scenario!

@brandon-pereira brandon-pereira requested review from pulpdrew and removed request for SpencerTorres October 3, 2025 20:59
@brandon-pereira
Copy link
Contributor Author

@pulpdrew if you have the capacity, mind reviewing this one?

pulpdrew
pulpdrew previously approved these changes Oct 6, 2025
Copy link
Contributor

@pulpdrew pulpdrew left a comment

Choose a reason for hiding this comment

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

LGTM, with two notes:

  1. It seems like we're also not persisting newlines in the select or order by inputs. Have we thought about applying this parser to those as well?
  2. It looks like nuqs handles newlines by default in v2.2.3. v2.2 also makes some improvements that would be great to have for testing purposes, which we have so far been missing out on. That's a major version update though, so fine by me to not tackle that upgrade as a part of this issue!

@brandon-pereira
Copy link
Contributor Author

brandon-pereira commented Oct 6, 2025

LGTM, with two notes:

1. It seems like we're also not persisting newlines in the select or order by inputs. Have we thought about applying this parser to those as well?

2. It looks like nuqs handles newlines by default [in v2.2.3](https://github.com/47ng/nuqs/pull/783). v2.2 also makes [some improvements](https://nuqs.dev/docs/testing) that would be great to have for testing purposes, which we have so far [been missing out on](https://github.com/hyperdxio/hyperdx/blob/main/packages/app/src/__tests__/timeQuery.test.tsx#L57). That's a major version update though, so fine by me to not tackle that upgrade as a part of this issue!
  1. Good catch, added support for those!
  2. Good idea, I created a ticket to bump the version (HDX-2558) so I can do better testing on that in isolation

@kodiakhq kodiakhq bot merged commit 1ed32e4 into main Oct 6, 2025
7 of 8 checks passed
@kodiakhq kodiakhq bot deleted the brandon/new-line-in-where-fix branch October 6, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants