implemented new ByteString for PoseidonID and GroupNames, with character warning#362
implemented new ByteString for PoseidonID and GroupNames, with character warning#362stschiff wants to merge 4 commits intoSchema_300_devfrom
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## Schema_300_dev #362 +/- ##
==================================================
+ Coverage 56.83% 56.86% +0.02%
==================================================
Files 33 33
Lines 4993 5066 +73
Branches 546 552 +6
==================================================
+ Hits 2838 2881 +43
- Misses 1609 1633 +24
- Partials 546 552 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
OK, I've added tests. This is ready for review. |
|
Nice! The conversions between String, Bytestring and Text are sometimes a bit awkward, but I still think you made the right decisions by choosing Bytestring as the main format. The code looks fine 👍 I ran commmunity-archiveaadr-archiveminotaur-archiveHow should we approach this reality? We still have to be able to read this old data. Maybe the strict validation should only happen for Poseidon v3.0.0+ packages? |
|
I had an alternative idea: trident could turn every unexpected character to |
|
Update on this issue from today's meeting: We've become unsure on whether it is still a good idea to introduce this restriction with Poseidon 3.0. To discuss this, I have opened a PR on the schema-repo |
|
OK, I've done this now. |
Previously, our type for
jPoseidonIDin the Janno Structure wasString. I have now changed this to anewtypebased on ByteString. I have also changedGroupNameto now be also based on ByteString, which makes it more compatible with sequence-formats.I've implemented a smart constructor via
Makeable, which now checks for illegal characters.I still have to implement some tests, so not ready for review just yet.