Skip to content

fix: parsing null values in cli #1106

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

Merged
merged 4 commits into from
Jul 11, 2025
Merged

fix: parsing null values in cli #1106

merged 4 commits into from
Jul 11, 2025

Conversation

ChiragAgg5k
Copy link
Member

@ChiragAgg5k ChiragAgg5k commented Jul 11, 2025

What does this PR do?

  • fix parsing of null values like default when making database operations
  • improve attribute recreating warning message

Test Plan

before:
Screenshot 2025-07-11 at 12 28 27 PM

after:
Screenshot 2025-07-11 at 12 48 16 PM


attribute recreation:
image

Related PRs and Issues

Have you read the Contributing Guidelines on issues?

yes.

@@ -844,10 +844,14 @@ const attributesToCreate = async (remoteAttributes, localAttributes, collection,

if (!cliConfig.force) {
if (deleting.length > 0 && !isIndex) {
log(`Attribute deletion will cause ${chalk.red('loss of data')}`);
console.log(`${chalk.red('-------------------------------------------------------')}`);
console.log(`${chalk.red('| WARNING: Attribute deletion will cause loss of data |')}`);
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should replace will with may.
Will sounds too strict, too powerful. For example when collection dont have any documents yet, the warning isnt relevant

@Meldiron Meldiron merged commit 4b363a1 into master Jul 11, 2025
37 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.

2 participants