playframework / playframework/play-socket.io

Play 2.7 support

Open
#16 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #89 by @wsargent — closed without merging
Dominant language
Scala
Stars
96
Forks
33
PR merge metrics
No merged PRs in 30d

Description

Is this project still supported? Plugins are quite old, Play 2.7 is also a must have, because of WebSocket issues fixed in that version.

We have created a fork where we have a branch with updated plugins, updated SBT, support for Play 2.7 (binary incompatibility with 2.6), I can create a pull request with those changes. Probably we should add support for both play version at once, creating appropriate builds and appending play version to package version.

Currently, it can be used using Jitpack https://jitpack.io/#iambotHQ/play-socket.io (use feature-play27 branch)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the feature-play27 branch in the reported fork and the closed pull request 89 to understand the attempted Play 2.7 support. Compare the updated plugins and SBT setup with the existing project, then verify whether builds can support Play 2.6 and 2.7 with distinct package versions. Done means the requested compatibility is implemented and usable without relying on the JitPack branch.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.