Skip to content

Conversation

blag
Copy link
Contributor

@blag blag commented May 19, 2025

I added on to #44, incorporating the feedback from that PR.

Additionally, since Nh3CharField and Nh3TextField ended up looking so similar, I just moved their logic into a mixin and tweaked their inheritance. This should also help anybody who is trying to write a custom field with Nh3, since they can now base theirs on Nh3FieldMixin.

Tests got a lot more complicated, and they would not allow two different models in different test modules (test_models_charfield.py and test_models_textfield.py) to be called the same thing. To ensure this wouldn't happen again I moved the test models and forms into their own respective modules.

Closes #44.
Resolves #45.

@blag
Copy link
Contributor Author

blag commented May 26, 2025

@marksweb This should be ready for review. 😄

@blag blag changed the title Nh3charfield and nh3textfield Nh3CharField and Nh3TextField May 27, 2025
@blag blag force-pushed the nh3charfield-and-nh3textfield branch from c62591f to 1759650 Compare July 22, 2025 00:47
@marksweb
Copy link
Owner

@blag I'm conscious that I don't get enough time for this, but keen to get this merged. Do you think it's possible to get a test to detect the warning so that can maintain 100% coverage?

@blag
Copy link
Contributor Author

blag commented Jul 24, 2025

Added the test like you asked. Coverage should be 100% now.

Thanks for creating this project; really appreciate your effort.

@marksweb marksweb merged commit e88cd26 into marksweb:main Jul 25, 2025
7 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.

[FEATURE REQUESTS] Provide Nh3CharField and Nh3TextField
3 participants