Oh interesting, I assume you don't mean the first letter but following letters?

https://github.com/faker-js/faker/blob/7327e6e6fd4061f10647a5fabf437406c9ee8066/src/locales/en_CA/address/postcode.ts

We don't have a strategy yet for post validating content generated by pattern 🤔

Could you provide some invalid generated postcodes? We can use these e.g. for negative tests.

For sure. Here are some examples.

P6V 1E1 is valid
V9O 9X4 is invalid
P7F 8L6 is invalid
G6O 7V0 is invalid
L6D 1K9 is invalid
E0T 2W7 is valid
G3L 4T8 is valid
E3P 6X3 is valid
J9A 4E7 is valid
N1Y 4H9 is valid

The following script can be used to generate more examples.

const { faker } = require('@faker-js/faker');

faker.locale = 'en_CA';

for (let i = 0; i < 10; i++) {
  const code = faker.address.zipCode();

  if (code.match(/^[ABCEGHJ-NPRSTVXY]\d[ABCEGHJ-NPRSTV-Z][ -]?\d[ABCEGHJ-NPRSTV-Z]\d$/)) {
    console.log(`${code} is valid`);
  } else {
    console.log(`${code} is invalid`);
  }
}

Our internal resources are currently filled with preparing the move to start with v8, So I'm sorry if we cannot handle a fix right now.
Also we might think about a robust strategy to handle this bug in a higher order.

Until then, would it be okay to just use a loop until a valid postcode was generated?

No problem, I can work around it. Thanks for the quick response!

@dbertouille Sorry, we kind of forgot about this issue.

Are you willing to create a PR for this now?
If yes, please check and update the pattern here:

• https://github.com/faker-js/faker/blob/next/src/locales/en_CA/location/postcode.ts

You might have to duplicate some lines

e.g.

'A#? #?#' -> 'A#A #E#' + 'A#F #X#' + ...

Maybe multiply it out fully and then pick 100 random patterns?

I created a PR to fix this issue:

• refactor(locale): fix en_CA postcode patterns #3235

Until the PR is merged, you can use the following workaround:

const zipCode = faker.helpers.fake('{{helpers.fromRegExp("[ABCEGHJ-NPRSTVXY][0-9][ABCEGHJ-NPRSTV-Z] [0-9][ABCEGHJ-NPRSTV-Z][0-9]")}}');