changepack / changepack Goto Github PK

Pullable is located in app/controllers/concerns/pullable.rb. It is included in controllers like app/controllers/repositories_controller.rb and app/controllers/teams_controller.rb.

As I said in the title, send an Update::Done event whenever Update#done is saved as true.

Write tests for write/lib/update/on_upserted.rb

app/controllers/api/v1/images_controller.rb is tested in spec/requests/api/v1/images_controller_spec.rb. Add a second test case that tests whether render status: :unprocessable_entity is rendered.

SourcesController is in app/controllers/sources_controller.rb

Changepack incorporates a concept from Domain-Driven Design called Bounded Context.

Bounded Context is a principle where a large system is divided into smaller, more manageable contexts, each with a clearly defined boundary and responsibility. These contexts encapsulate specific areas of the domain and help maintain a clear separation of concerns.

In the case of Changepack, we divided the app into several contexts such as platform, connect, write, and so on. Within each context, we place relevant models, events, handlers and so on. This encapsulates common business logic within a single context. Each bounded context has a README, too.

Please have a look at paths such as /platform, /write, or /connect and based on that template create a new /broadcast context which will deal with broadcasting new posts to channels such as email, Slack, or Intercom. For now we’re going to need:

• A basic README
• write/lib/post.rb: the Post model needs to send an event like Post::Published whenever it is transitioned to published state. You can have a look at Post#publish from write/lib/post/publish.rb.
• To see how events are structured, you can review an example from write/lib/summary/events.rb.
• In the new broadcast context, we need an event handler that will react to Post::Published and for now just return an ID of the newly published post.
• To see how event handlers are structured, you can review an example from write/lib/summary/on_requested.rb.

Footer is located in app/views/components/i/footer.rb

Testing Phlex views in Rails

When you include Phlex::Testing::Rails::ViewHelper, views rendered in the test will have a view context, so they can use Rails helpers.

Here’s an example of a test in Minitest:

require "phlex/testing/view_helper"

class TestHello < Minitest::Test
	include Phlex::Testing::ViewHelper

	def test_hello_output_includes_name
		output = render Hello.new("Joel")
		assert_equal "<h1>Hello Joel</h1>", output
	end
end

Please remember that I want you to use RSpec.

Write tests for write/lib/summary/on_new_day.rb

getting weird rails errors when trying to sign up.

RoutesHelper is located in app/helpers/routes_helper.rb

In app/views/devise/shared/_links.html.slim, there’s an option to sign in with multiple OmniAuth providers. (Currently we support GitHub and Linear.) Right now the links will be positioned centrally, but each link will repeat "Sign in with…" and be a separate block, meaning that multiple providers will create a long list of links. I want you to rework the layout of that section so that each link is sequenced in an inline position, similar to "Sign in with GitHub • Linear • (and so on, and so on…)"

CI configuration can be found in .github/workflows/ci.yml