Fix RDAP quirks uncovered during documentation

There's no reason not to allow a one-character search string when there are no wildcards. And the ROID validity pattern did not allow underscores, which was causing problems with our ROIDs.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=136256605
This commit is contained in:
mountford 2016-10-15 13:33:11 -07:00 committed by Ben McIlwain
parent 861fd60d2c
commit f1ad34b12f
5 changed files with 24 additions and 14 deletions

View file

@ -72,6 +72,14 @@ public class RdapSearchPatternTest {
RdapSearchPattern.create("ex*am.lol", true);
}
@Test
public void testShortString_ok() throws Exception {
RdapSearchPattern rdapSearchPattern = RdapSearchPattern.create("e", true);
assertThat(rdapSearchPattern.getInitialString()).isEqualTo("e");
assertThat(rdapSearchPattern.getHasWildcard()).isFalse();
assertThat(rdapSearchPattern.getSuffix()).isNull();
}
@Test
public void testPrefixTooShort_unprocessable() throws Exception {
thrown.expect(UnprocessableEntityException.class);