Skip to content

Conversation

@emohk
Copy link

@emohk emohk commented Jul 8, 2025

Checklist

  • I have read the OpenWISP Contributing Guidelines.
  • I have manually tested the changes proposed in this pull request.
  • I have written new test cases for new code and/or updated existing tests for changes to existing code.
  • I have updated the documentation.

Reference to Existing Issue

Closes #673 .

Description of Changes

Replaced all uses of third-party with Django’s built-in and added corresponding migrations. Django applies the type conversion automatically using the appropriate SQL command, ensuring that existing data remains safe.

@emohk emohk force-pushed the issues/673-use-built-in-jsonfield branch from c6f5410 to b62f072 Compare July 8, 2025 19:30
@emohk emohk force-pushed the issues/673-use-built-in-jsonfield branch from b62f072 to 3975f34 Compare July 18, 2025 09:55
…p#673

Replaced all uses of third-party  with Django’s built-in  and added corresponding migrations.
Django applies the type conversion automatically using the appropriate SQL command, ensuring that existing data remains safe.

Fixes openwisp#673
@emohk emohk force-pushed the issues/673-use-built-in-jsonfield branch from 3975f34 to 8d7c713 Compare August 13, 2025 04:35
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.

[change:monitoring] Replace thirdparty JSONField with Django built in JSONField

1 participant