Reminder: Should have a /try section powered by opal-rspec
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 15
- Forks
- 41
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
@dchelimsky @elia @adambeynon @opalrb Amazing. Would be cool to include something like that on the new rspec site /cc @mootpointer
Demo:
http://opal.github.io/opal-playground/rspec/
Code:
https://github.com/opal/opal-playground/blob/master/source/rspec.html.haml
https://github.com/opal/opal-playground/blob/master/source/javascripts/playground-rspec.js.rb
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked demo and its source files, source/rspec.html.haml and source/javascripts/playground-rspec.js.rb, to understand how the /try experience is assembled with opal-rspec. Compare that integration with the rspec.github.io site structure. Done means the site includes a working /try section powered by the demonstrated setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100