microsoft / microsoft/pxt-microbit

Name in extension dialog is different when searching

Open
#7,072 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

extension P2
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

Describe the bug

Arising from https://support.microbit.org/helpdesk/tickets/94998 (private)

In the extension dialogue, the extension name is different after a text search, compared with other cases

See example pictures below.

I think there are 3 cases:

  • search for a URL (as when developing an extension)
  • search for text
  • select the category (e.g. Robotics)

After searching for text, the name appears to be based on the GitHub repo URL, whereas others cases show the pxt.json name field.

I knew the text is taken from the repo About when searching for text, though I can't think why, but the name change was a surprise.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new project
  2. Click on Extensions
  3. Look for extensions
  4. See difference

Expected behavior

I expect the name to be the same, because I can't think of a reason for it to change. The same applies to the text.
Is this documented?
Is there a way to override the default behaviour?

Screenshots

Examples for https://github.com/robotgyms/pxt-robotpu

Search for URL

Image

Search for text "pu"

Image

Select Robotics category

Image

micro:bit version (please complete the following information):
not hardware related

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows
  • Browser [e.g. chrome, safari] Chrome
  • Version [e.g. 22]

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.

Research direction

Start by reproducing the extension dialog behavior in pxt-microbit using the three paths described: URL search, text search, and category selection. Trace how each path obtains the extension name and description, especially the text-search result and the pxt.json name field. Done means the displayed extension information is consistent across the three cases, with tests or a repeatable verification covering the change.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.