Cross Project Usage

Open
#5 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
api, backend-api-design

Research direction

Start by tracing AyonCppApi construction and how AYON_PROJECT_NAME is read. Define how multiple projects would be registered through the API and how cross-project resolution should select them. Done means the API supports multiple registered projects without relying on a single project environment variable.

Written by the indexing model from the issue text.

Description

Currently, when an AyonCppApi instance is created, it needs the AYON_PROJECT_NAME environment variable to get overwrites from the server.
It would be great if we find a way to allow for multiple projects to be registered, maybe allow adding projects via func() call so that cross-project resolution is possible

Dominant language
C
Stars
2
Forks
3
Avg merge
5d 2h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ynput/ayon-cpp-api

All issues in ynput/ayon-cpp-api

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.