Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
cameo
cameo
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • Cameo
  • cameocameo
  • Issues
  • #89

Closed
Open
Opened Oct 13, 2020 by yannick legoc@legoc
  • Report abuse
  • New issue
Report abuse New issue

Define future C++ and Java API class names in Python API

As Python API is not used yet, we can already define the future names, i.e. App instead of Instance. We need to fix the names.

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
Python API
Milestone
Python API
Assign milestone
Time tracking
None
Due date
None
1
Labels
suggestion
Assign labels
  • View project labels
Reference: cameo/cameo#89