Skip to content

fix(fo/vn): strip the FO prefix in compact#161

Open
spokodev wants to merge 1 commit into
koblas:mainfrom
spokodev:fix/fo-vn-strip-fo-prefix
Open

fix(fo/vn): strip the FO prefix in compact#161
spokodev wants to merge 1 commit into
koblas:mainfrom
spokodev:fix/fo-vn-strip-fo-prefix

Conversation

@spokodev

@spokodev spokodev commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Faroe Islands V-numbers are frequently written with the FO country prefix (e.g. FO384941). compact does not remove it, so the value is 8 characters and validation fails with InvalidLength.

Strip a leading FO in clean, following the same approach already used for the BE prefix in be/vat and matching the upstream python-stdnum reference (validate('FO384941')'384941').

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Faroe Islands V-number validation logic to correctly handle inputs prefixed with 'FO'. By stripping this prefix during the cleaning phase, the validator ensures that such inputs are processed correctly rather than failing due to invalid length, aligning the implementation with upstream standards.

Highlights

  • Prefix handling: Added logic to the clean function to strip the 'FO' country prefix from Faroe Islands V-numbers.
  • Test coverage: Added a new test case to verify that 'FO384941' is correctly compacted to '384941'.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the validation logic for FO numbers by stripping the 'FO' prefix in the clean function and adds a corresponding test case. The reviewer suggested simplifying the clean function by utilizing the third parameter of cleanUnicode to strip the prefix, which also avoids using the deprecated substr method.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread src/fo/vn.ts
Comment on lines 18 to 29
function clean(input: string): ReturnType<typeof strings.cleanUnicode> {
return strings.cleanUnicode(input, ' -.');
const [value, err] = strings.cleanUnicode(input, ' -.');

if (err !== null) {
return [value, err];
}
if (value.startsWith('FO')) {
return [value.substr(2), null];
}

return [value, null];
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The cleanUnicode utility function already supports a third parameter stripPrefix to automatically strip a prefix (or list of prefixes) after cleaning and converting to uppercase.

Using this built-in parameter simplifies the implementation and avoids the use of the deprecated String.prototype.substr() method.

function clean(input: string): ReturnType<typeof strings.cleanUnicode> {
  return strings.cleanUnicode(input, ' -.', 'FO');
}

@koblas koblas left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see gemini feedback

@spokodev spokodev force-pushed the fix/fo-vn-strip-fo-prefix branch from 0fa99c0 to d88a600 Compare July 8, 2026 20:15
@spokodev

spokodev commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Thanks — refactored clean() to strip the FO prefix via cleanUnicode's third argument, matching se/vat and the other prefix modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants