Skip to content

Inconsistent API naming #2636

Closed
Closed

Description

@Rot127

Ensure cs_ prefix for all API structs, ids and function names?

Not all API structs and functions have the cs_ prefix. This leads to issues like these: #2316

The question is now, should this be addressed before the v6 Beta? Or before v6 Gold?

Or is API stability more important for everyone and we just keep it as is?

Currently the naming was kinda arbitrary. Sometimes only the arch_ prefix, sometimes cs_arch_.

Activity

  1. modified the milestones: v6 - Gold, v6 - Beta on Feb 26, 2025
  2. added and removed
    bugSomething is not working as it should
    on Feb 26, 2025
  3. locked and limited conversation to collaborators on Feb 26, 2025
  4. converted this issue into a discussion #2637 on Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions