Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ChangeOrder doesn't set desired priorities

See original GitHub issue

General information

Library version: v8.2.0

Issue description

I added a custom card (custom-card) with some validator closely related to Maestro, then I changed my custom-card order to position 0 but I still get maestro coming up as the card type.

I debugged using Validate.creditCardType(''), and I was able to verify that my custom-card was in position 0.

Thanks for the awesome library. Looking forward to getting some feedback.

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

crookedneighborcommented, Sep 3, 2019

This is expected behavior for card validator.

It will only mark something as valid when it determines that there is only one possible card type. Since 506 can match either maestro or your custom card, that’s the expected outcome. Sounds like you need to make your custom card more specific for what ranges it supports (and possibly update the maestro card pattern as well)

0reactions

ooadecommented, Sep 3, 2019

Thanks 😃

Top Results From Across the Web

A Better Way to Set Strategic Priorities

A better way to establish priorities is to put rank ordering aside and return to first principles. To wit: There are three interdependent ......

Processing conversation with priority order - rusanu.com

If you do use related conversations, I really cannot see a situation when one priority is desired for a conversation in the group...

How to Rank and Set Strategic Priorities | HighGear

Perhaps the best way to remain agile and establish priorities within a changing environment is to start at the top with executive and...

Filter order in spring-boot - java - Stack Overflow

It should go last. From JavaDoc of @Order: Lower values have higher priority. The default value is Ordered.LOWEST_PRECEDENCE, indicating lowest priority (losing ...

Solved: rank and priority sorting - Jira - Atlassian Community

Solved: Hi, The backlog is ordered by default by rank and we have the rank functionnality to have the drag n drop functionnality....