Did we remove the validation for ue_version_major and resource_id being the correct number of bits?

[PLeVasseur]

I was looking to use this today and seems like it was not migrated over when we had core API changes a while back.

I see in here @sophokles73 seems to have removed (?) the concept of validating the length of bits contained in the ue_version_major and resource_id.

Maybe I'm missing something though?

I like how UUri::try_from_parts will give us a correct-by-construction UUri, but I'd like the ability to verify that a UUri that I'm given matches the correct specification here.

Perhaps we removed the ability to check this?

Can I get a sanity check here before I reimplement this?

[sophokles73]

Hmm, when parsing a UUri from a URI string we do check that it is an 8 bit unsigned integer. But when we serialize to a URI string we do not. I guess you are right in that we should check there too. Is that what you are concerned about?

[PLeVasseur]

Yeah, validating a UUri that's of unknown provenance is what I was getting at. I think you've understood my ask and are working to implement the ability to do that in #210.