discourse/spec/components/content_buffer_spec.rb
Sam Saffron 4ea21fa2d0 DEV: use #frozen_string_literal: true on all spec
This change both speeds up specs (less strings to allocate) and helps catch
cases where methods in Discourse are mutating inputs.

Overall we will be migrating everything to use #frozen_string_literal: true
it will take a while, but this is the first and safest move in this direction
2019-04-30 10:27:42 +10:00

32 lines
993 B
Ruby

# frozen_string_literal: true
require 'rails_helper'
require 'content_buffer'
describe ContentBuffer do
it "handles deletion across lines properly" do
c = ContentBuffer.new("a\nbc\nc")
c.apply_transform!(start: { row: 0, col: 0 }, finish: { col: 1, row: 1 }, operation: :delete)
expect(c.to_s).to eq("c\nc")
end
it "handles deletion inside lines properly" do
c = ContentBuffer.new("hello world")
c.apply_transform!(start: { row: 0, col: 1 }, finish: { col: 4, row: 0 }, operation: :delete)
expect(c.to_s).to eq("ho world")
end
it "handles inserts inside lines properly" do
c = ContentBuffer.new("hello!")
c.apply_transform!(start: { row: 0, col: 5 }, operation: :insert, text: " world")
expect(c.to_s).to eq("hello world!")
end
it "handles multiline inserts" do
c = ContentBuffer.new("hello!")
c.apply_transform!(start: { row: 0, col: 5 }, operation: :insert, text: "\nworld")
expect(c.to_s).to eq("hello\nworld!")
end
end