670e6a33f8
There are two motivations for this: 1. It looks like we're going to add other features that require server-side storage (e.g. user notes). 2. Namespacing glitchsoc modifications is a good idea anyway: even if we do not end up doing (1), if upstream introduces a keyword-mute feature that also uses a "KeywordMute" model, we can avoid some merge conflicts this way and work on the more interesting task of choosing which implementation to use.
8 lines
183 B
Ruby
8 lines
183 B
Ruby
class MoveKeywordMutesIntoGlitchNamespace < ActiveRecord::Migration[5.1]
|
|
def change
|
|
safety_assured do
|
|
rename_table :keyword_mutes, :glitch_keyword_mutes
|
|
end
|
|
end
|
|
end
|