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

Develop #1480

Merged
merged 89 commits into from
Jan 30, 2024
Merged

Develop #1480

merged 89 commits into from
Jan 30, 2024

Conversation

Dinika
Copy link
Contributor

@Dinika Dinika commented Jan 30, 2024

Fixes #

Description

How has this been tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added necessary unit and integration tests.
  • I have added screenshots (if applicable), in the comment section.

danburonline and others added 30 commits December 4, 2023 14:43
… chore/add-vs-debugger

# Conflicts:
#	src/shared/containers/ResourceViewActionsContainer.tsx
Two type errors are currently still
suppressed. I need to fix them.
However, the logic works already.
Two remaining.
Still some TODOs left to improve
this sub view and its logic.
danburonline and others added 28 commits January 12, 2024 10:37
However, doesn't work now if there
are two resource types, such as
`ElasticSearchView` and `View`.

Need to fix this in the
coming commit(s).
Instead of disallowing the starting of
all fields with an underscore, I now
only allow the topmost fields to not
start with an underscore.
Undeprecate other resource types (`schemas`, `views` and `storages`)
One test remaining...
Fixed edge case.
     automatically decoded

This is a temporary solution until we update react-router to v6

If a nexus id has some encoded chars (like - https://hello.lol/https%3A%2F%2Fencoded.url%2Fwow),

history.push pushes this to window.location:
https%3A%2F%2Fhello.lol%2Fhttps%3A%2F%2Fencoded.url%2Fwow

instead of:
https%3A%2F%2Fhello.lol%2Fhttps%253A%252F%252Fencoded.url%252Fwow

Using an older version of `history` and forcing all fusion dependencies
to use this version is working for now.

This solution is taken from remix-run/history#505 (comment)

Signed-off-by: Dinika Saxena <[email protected]>
Adjust custom linter logic for code editor
@bilalesi bilalesi merged commit 512b5a9 into main Jan 30, 2024
2 checks passed
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.

3 participants