Optional Parameters Trailing Slash no longer matched

[amcdnl]

After updating to 12 and 13, I'm getting unmatched params on the following route:

$stateProvider.state('record', {
    url: '/record/{appId}/{recordId:[0-9a-fA-F]{10,24}}',
    params: { 
        appId: { value: null },
        recordId: { value: null }
    },
    views:{
        '': {
            controller: 'RecordCtrl',
            templateUrl: 'app/record/record.tpl.html'
        }
    }
});

when I goto a url like:

 <a href="/myapp/record/546a3e4dd273c60780e35df3/">

per @christopherthielen this is because of the trailing slash introduced in the new version. Reference: #1032

[christopherthielen]

This is due to the {10,24} in the recordId regex. Changing it to a "*" allows the pattern to match. See this failing test case I am adding:

      it("should populate even if the regexp requires 1 or more chars", function() {
        var m = new UrlMatcher('/record/{appId}/{recordId:[0-9a-fA-F]{10,24}}', {
          params: { appId: null, recordId: null }
        });
        expect(m.exec("/record/546a3e4dd273c60780e35df3/"))
          .toEqual({ appId: "546a3e4dd273c60780e35df3", recordId: null });
      });

[christopherthielen]

I thought we accounted for this by making the capture group optional, but apparently it's not working how I think it is. Thanks for the bug report.

[oleduc]

+1

[bastienlau]

+1

[christopherthielen]

@amcdnl this matches your pattern

var m = new UrlMatcher('/record/{appId}/{recordId:[0-9a-fA-F]{10,24}}', {
params: { appId: null, recordId: { value: null, squash: true } }
});

granted, you shouldn't have to do this.

[amcdnl]

@christopherthielen I tried manually inserting this code and still no dice. I added the squash too.

Note: I'm using future states too, not sure if that has anything to do with it.