Skip to content

Restructure ContentClient and related encoder/decoder modules #2

@RaptorFlav

Description

@RaptorFlav

Ultimately, the idea is to allow users to do:

defmodule MyContentClient do
  use Pepper.HTTP.ContentClient,
    encoders: my_encoders,
    decoders: my_decoders
end

The reasoning? Compiler warnings for custom encoder and decoder modules that will be compiled AFTER pepper is compiled, these floating references will cause scary warnings for users, plus it affects the global ContentClient, which is annoying at its best and dangerous at its absolute worst, the library's default ContentClient should be "sacred" and unchangeable even for config, if clients want a custom version they can create one using the above macro.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions