-
Notifications
You must be signed in to change notification settings - Fork 3
chore: merge master to staging for Sprint A18S20 #269
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix: force re-download of data when building database
…-layout-sync chore(common): loosen .keyman-touch-layout schema layer id requirements
Fixes #244. Widens the field to support 3-digit numeric subtags. There may be other metadata we wish to support in the future, but this at least allows the database to build, and searches to return the keyboard in question, verified locally (no tests added at this point).
fix: allow numeric region subtags
Fixes: #247 Fixes: API-KEYMAN-COM-2K
We no longer do anything with crash reports from early versions of Keyman, so there's no point in collecting the data. This also resolves a crash when handling some reports. This also removes the need to have the api_keyman_com_github_user and api_keyman_com_github_repo variables defined, which will be cleaned up as a future task. Fixes: #249 Fixes: API-KEYMAN-COM-4H
Moves the filtering earlier in order to get the benefit in the returned object as well as in what we pass to the database. Fixes: #251 Fixes: API-KEYMAN-COM-1
CleanQueryString should only be cleaning the plain search text...
Part of #253. Also fixes null language description from keyboard_info
…g-17 fix: select first matching language name where there are conflicts, and fix null language description
…ngth-for-fulltext-search fix: reduce query string length for full text searches
…eption-handler chore: remove exception handler for Keyman Desktop 10
…ies-in-language-examples fix: handle missing properties in language examples
chore: Update BOOTSTRAP_VERSION to 0.7
chore: Update BOOSTRAP_VERSION to 0.8
…ents chore: cleanup comments in .htaccess (and remove junk files)
feat: annual statistics for reporting
Relates-to: keymanapp/keyman.com#494 Depends-on: keymanapp/shared-sites#38
chore: support debug mode
Discourse API changed with a recent update to community.software.sil.org. Fixes: keymanapp/keyman#12678
…post fix(windows): track discourse field name change for upload.json
chore: add new issues to Keyman project automatically
…heck chore: disable database readiness check
…-to-staging-a18s20
mcdurdin
approved these changes
Jan 30, 2025
Member
mcdurdin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Staging branch got stale over the past year, so this brings it up to date, and hopefully addresses the crash in #267