Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Share Error code tables across components

Open
#128 0 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
go
Domain
tooling

Research direction

The issue names no files, tests, or entry points. Start by locating how component error codes are defined and how XML configuration is parsed, then determine how a shared globalerrors.xml would be loaded across components. Done should include an agreed design for shared codes and exception propagation, plus coverage for the import behavior.

Written by the indexing model from the issue text.

Description

It would be great to have a way to globalize error codes across different components. This would make it very powerful for developing distributed applications and plugin concept, and could include "exception propagation" for injected components.

The simplest concept would be just to have a line like

which then reads in central error codes.

Dominant language
Go
Stars
54
Forks
26
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 Autodesk/AutomaticComponentToolkit

All issues in Autodesk/AutomaticComponentToolkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.