Skip to content

Conversation

@fkrauthan
Copy link
Contributor

@fkrauthan fkrauthan commented Feb 2, 2025

Correctly parses R08R/5000VP6000FT/D and setting the indicator field (in the example case to ValueIndicator.GreaterThan)

This fixes #117

@aeharding
Copy link
Owner

Hi! Thanks for the PR. Corepack dropped the ball and broke the build so if you rebase on latest main and force push it should start working again.

@fkrauthan fkrauthan marked this pull request as draft February 2, 2025 18:40
@fkrauthan
Copy link
Contributor Author

Did the rebase and marked it as draft for now. I want to do some validation to make sure that this was not just issued by error and is actually a use-case.

@fkrauthan fkrauthan marked this pull request as ready for review February 4, 2025 06:47
@fkrauthan
Copy link
Contributor Author

Ok yeah I've confirmed it can happen (even if very rare)

@fkrauthan
Copy link
Contributor Author

@aeharding you think you get a chance anytime soon to review, merge and release? I am getting ready to publish a new update for my site and would love to include it.

@aeharding
Copy link
Owner

aeharding commented Feb 11, 2025 via email

@fkrauthan
Copy link
Contributor Author

Just checking in if this is still on your radar?

@aeharding
Copy link
Owner

Sorry, yes it looks good.

@aeharding aeharding merged commit c9cbfb5 into aeharding:main Mar 1, 2025
1 check passed
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.

Value indicator for RVR in METAR with min and max range is not parsed correctly

2 participants