Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
clean-platform
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • clean-and-itasks
  • clean-platform
  • Merge Requests
  • !274

Merged
Opened Sep 10, 2019 by Steffen Michels@smichelsMaintainer

standards: make more explicit for which classes instances should be provided

  • Overview 3
  • Commits 2
  • Pipelines 2
  • Changes 1

I think it makes sense to provide instances for the Gast classes for types in clean-platform. Such instances can then be reused when defining tests. Do you agree @cstaps, @baslijns, @mlubbers? Then last one who agrees has to merge :)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Reference: clean-and-itasks/clean-platform!274
Source branch: gastInstances

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.