Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resources: fix Directions types #5981

Merged
merged 1 commit into from
Dec 6, 2023
Merged

resources: fix Directions types #5981

merged 1 commit into from
Dec 6, 2023

Conversation

quisquous
Copy link
Owner

The OutputStrings type itself is already a dictionary. This ~mostly worked before, but prevented you from saying something like outputStrings: Directions.outputStrings8Dir directly as the types would no longer match up.

The OutputStrings type itself is already a dictionary.
This ~mostly worked before, but prevented you from saying
something like `outputStrings: Directions.outputStrings8Dir`
directly as the types would no longer match up.
@quisquous quisquous merged commit 611bec6 into main Dec 6, 2023
5 checks passed
@quisquous quisquous deleted the directions_types branch December 6, 2023 18:41
github-actions bot pushed a commit that referenced this pull request Dec 6, 2023
The OutputStrings type itself is already a dictionary. This ~mostly
worked before, but prevented you from saying something like
`outputStrings: Directions.outputStrings8Dir` directly as the types
would no longer match up. 611bec6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant