For larger applications we are splitting experience apis into multiple projects. This changes the format of the http.listener path that mulint checks and mulint is flagging as error:
Example:
policyholder-account-web-exp-api listens on /api/policyholder/v1/accounts/
policyholder-billing-web-exp-api listens on /api/policyholder/v1/billing/
mulint output:
policyholder-account-web-exp-api.xml http:listener path: expected matching /^\/(?:console|api)\/.+\/v1\/*$/ but was "/api/policyholder/v1/accounts/"
policyholder-account-web-exp-api.xml http:listener path: expected matching /^\/(?:console|api)\/.+\/v1\/*$/ but was "/console/api/policyholder/v1/accounts/"
For larger applications we are splitting experience apis into multiple projects. This changes the format of the http.listener path that mulint checks and mulint is flagging as error:
Example: policyholder-account-web-exp-api listens on /api/policyholder/v1/accounts/ policyholder-billing-web-exp-api listens on /api/policyholder/v1/billing/
mulint output: policyholder-account-web-exp-api.xml http:listener path: expected matching /^\/(?:console|api)\/.+\/v1\/*$/ but was "/api/policyholder/v1/accounts/" policyholder-account-web-exp-api.xml http:listener path: expected matching /^\/(?:console|api)\/.+\/v1\/*$/ but was "/console/api/policyholder/v1/accounts/"