-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
use_restrictions vs. use_turn_restrictions #808
Comments
Good catch. Will change that |
wonder why this haven't been caught by the tests? |
Bad grepping on my part. The foot profile has defined |
This is not a functional bug, but inconsistent naming, right? |
Yes. If the variable is not defined in the profile, turn restrictions default to being enabled. |
ok, thanks for this piece of info. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code and profile don't seem to agree what the turn restriction parameter should be called. All profiles refer to it as
use_restrictions
(e.g. car.lua) while Extractor/BaseParser.cpp looks foruse_turn_restrictions
.The text was updated successfully, but these errors were encountered: