Remove invalid singer-decimal formats in locations schema#120
Merged
Conversation
This reverts commit 6c0aacb.
kgerxhi
approved these changes
Oct 30, 2024
singer-decimal to singer.decimal in locations schemasinger-decimal in locations schema
singer-decimal in locations schemasinger-decimal format in locations schema
singer-decimal format in locations schemasinger-decimal formats in locations schema
dmosorast
approved these changes
Nov 4, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of change
singer-decimalformat fromlatitudeandlongitudein thecoordinatesfield from thelocationsstreamManual QA steps
string.Risks
singer-decimalwas never a valid format.Rollback steps
AI generated code
https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code