akka/akka-http

Lack of ws.Message (un)marshaller

Open

#2,256 opened on Oct 14, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Scala (598 forks)batch import
1 - triagedhelp wantedt:marshallingt:websocket

Repository metrics

Stars
 (1,311 stars)
PR merge metrics
 (Avg merge 1d 10h) (2 merged PRs in 30d)

Description

I'd like to hear opinions on the standard inclusion of a FromWSMessageUnmarshaller for ws.Message. This would reduce standard boilerplate when dealing with web sockets. I'd even go as far as suggest that implementations for JSON and XML be included. Whenever I'm dealing with web sockets, most, if not all, communication is done using a JSON transport. I've got the implementations mostly ready, so I can produce a PR if necessary.

Contributor guide

Research direction
Implement a FromWSMessageUnmarshaller for ws.Message: study existing marshalling patterns in akka http, then create JSON and XML implementations using Jackson/XStream or built in marshallers; consider contributing to the akka http contrib repository or creating a separate library.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaAkka HTTP basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60