openclaw - 💡(How to fix) Fix [Feature Request]: Show human-readable Telegram forum topic names in Control UI session selector [1 participants]

Fix Plan

To address the issue, we will implement a combination of the suggested approaches:

1. Fetch topic names from the Telegram API at startup via getForumTopics and cache them in gateway state.
2. Allow a name field in per-topic config as a fallback.

Step-by-Step Solution

• Fetch topic names from Telegram API:
  • Use the getForumTopics method to retrieve topic names from the Telegram API.
  • Cache the topic names in the gateway state for future use.
• Allow a name field in per-topic config:
  • Update the configuration schema to include a name field for each topic.
  • Use the name field as a fallback when topic names cannot be fetched from the Telegram API.
• Update the Control UI:
  • Modify the session selector to display the topic names instead of raw session keys.
  • Use the cached topic names or the name field from the configuration as the display name.

Example Code

// Fetch topic names from Telegram API
const fetchTopicNames = async (groupId) => {
  const response = await telegramApi.getForumTopics(groupId);
  const topicNames = response.topics.reduce((acc, topic) => {
    acc[topic.id] = topic.name;
    return acc;
  }, {});
  return topicNames;
};

// Cache topic names in gateway state
const cacheTopicNames = (topicNames) => {
  // Implement caching logic here
};

// Update Control UI to display topic names
const getDisplayTopicName = (topicId, groupId) => {
  const cachedTopicNames = getCacheTopicNames(groupId);
  const topicName = cachedTopicNames[topicId];
  if (topicName) {
    return topicName;
  } else {
    // Fallback to name field in per-topic config
    const config = getConfig();
    const topicConfig = config.channels.telegram.groups[groupId].topics[topicId];
    return topicConfig.name;
  }
};

Verification

To verify that the fix worked, check the Control UI session selector and ensure that it displays the topic names instead of raw session keys. Test the following scenarios:

• Topic names are fetched successfully from the Telegram API.
• Topic names are cached correctly in the gateway state.
• The name field in per-topic config is used as a fallback when topic names cannot be fetched.
• The Control UI displays the correct topic names for each session.