Skip to content

What's the reason for having a json and xml part? #40

Closed
@ThomasLandauer

Description

@ThomasLandauer

While thinking about module's parts in general (see Codeception/Codeception#6026), one thing is still unclear: What's the reason for having the two parts in this module? Are there really situations where loading the entire REST module would lead to a conflict?

And what does it mean that e.g. at https://codeception.com/docs/modules/REST#amBearerAuthenticated both parts are listed? That you'll get this method if you load part json or xml or the entire module (i.e. no part key given at all)? => This is inconsistent with https://codeception.com/docs/modules/Symfony where part is not mentioned for most functions.

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