-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
return the default style first in the list #7172
Conversation
bd124bd
to
f6b5470
Compare
Looks good! Can you update the style test in test_provider_postgres to match? |
f6b5470
to
ba5019e
Compare
@nyalldawson I just added some tests. While I was writing the test, I realized that I always have a default style in my DB for my layers. So this patch works only when we are sure that there is a default style. I can add a function later to know if there is a default style. Is-it fine like this @nyalldawson ? BTW, are PG tests running on travis? or only locally? |
ba5019e
to
36cfc54
Compare
On travis also |
OK. Let me know if it's OK for 3.2 or 3.4. I will have some time in July about styles. |
36cfc54
to
f6b5470
Compare
f6b5470
to
7526725
Compare
In that case, do you think it's better to just add a new function to retrieve the default style? (returning an empty string if none is set) |
Yes, I'm planning to add this function as soon as the feature freeze is finished. |
Gentle ping to have one PR less in the pending queue for 3.2? |
Sure, let's merge. |
Thanks |
Description
With this fix, I know that 60 is the default style, 122 and 120 are other related styles, 129, 128 etc are non related styles.
It's the only way in the API to know the default style.
Checklist
fixes #11111
in the commit message next to the description[FEATURE]
in the commit message[needs-docs]
in the commit message and contain sufficient information in the commit message to be documentedscripts/prepare-commit.sh
script before each commit