You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we mark deprecation with the deprecates relation. This gives us one direction. However, this requires a secondary query to determine whether a keyboard is deprecated, which is not ideal for searches. We should build the corresponding relation for each keyboard as a deprecatedBy relation.
Then we need to update the search and cloud APIs to flag deprecated keyboards.
Currently, we mark deprecation with the
deprecates
relation. This gives us one direction. However, this requires a secondary query to determine whether a keyboard is deprecated, which is not ideal for searches. We should build the corresponding relation for each keyboard as adeprecatedBy
relation.Then we need to update the search and cloud APIs to flag deprecated keyboards.
This work comes out of keymanapp/keyboards#374.
The text was updated successfully, but these errors were encountered: