-
Notifications
You must be signed in to change notification settings - Fork 95
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
translations for w3c geo latitude and longitude, expose vocabulary short name #1081
Conversation
Kudos, SonarCloud Quality Gate passed!
|
Codecov Report
@@ Coverage Diff @@
## master #1081 +/- ##
============================================
- Coverage 60.32% 60.27% -0.06%
Complexity 1592 1592
============================================
Files 32 32
Lines 4429 4433 +4
============================================
Hits 2672 2672
- Misses 1757 1761 +4
Continue to review full report at Codecov.
|
Show short name of vocabulary for property values from another vocab
Fix typo in swagger.json offset description
Optimize alphabet letter query: use GRAPH instead of FROM
…graphical-translations
SonarCloud Quality Gate failed.
|
This PR looks a bit odd after rebasing (I thought I did it right but it seems like there was an existing (old) PR (which is this)) but the real comparison can be found here: https://github.com/NatLibFi/Skosmos/compare/geographical-translations. Reverted a change that made exposed vocabulary short name content language-aware (not shown in commit stack). Also switched from geo prefix into wgs84 which should be 100% explicit. |
No description provided.