Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming a project causes collapsed function added by Component Browser to stop working #11815

Open
radeusgd opened this issue Dec 9, 2024 · 17 comments
Assignees
Labels
--bug Type: bug -gui

Comments

@radeusgd
Copy link
Member

radeusgd commented Dec 9, 2024

See the video below:

Enso_i3Qapeb7xo.mp4

The issue stems from the fact that while the effect of Ctrl-G is Main.collapsed, once I add a new instance from Component Browser is not Main.<name> but ProjectName.<name>. Thus, once the project gets renamed, the reference is no longer valid.

We should either:

  • detect this on rename and apply necessary edits (relatively hard),
  • fix the Component Browser entry to suggest Main.<name> or just <name> for the local symbol, so its name is not tied with the current project.
@radeusgd radeusgd added --bug Type: bug -gui labels Dec 9, 2024
@github-project-automation github-project-automation bot moved this to ❓New in Issues Board Dec 9, 2024
@farmaazon farmaazon added this to the 2024-End-Of-Year milestone Dec 10, 2024
@farmaazon farmaazon moved this from ❓New to 📤 Backlog in Issues Board Dec 12, 2024
@farmaazon
Copy link
Contributor

Refinement notes:

  • Let's put Main in this special case of current project.
  • Removing and module name is a harder task, because we need to care about all possible name collisions.

@kazcw kazcw self-assigned this Dec 16, 2024
@kazcw kazcw moved this from 📤 Backlog to 🔧 Implementation in Issues Board Dec 16, 2024
@enso-bot
Copy link

enso-bot bot commented Dec 17, 2024

Keziah Wesley reports a new STANDUP for yesterday (2024-12-16):

Progress: Refactoring qualified names in suggestion DB to be independent of project QN. It should be finished by 2024-12-20.

Next Day: Next day I will be working on the #11815 task. Finish, start next task.

@enso-bot
Copy link

enso-bot bot commented Dec 18, 2024

Keziah Wesley reports a new STANDUP for yesterday (2024-12-17):

Progress: Refactoring suggestion DB / CB to use parsed QNs. It should be finished by 2024-12-20.

Next Day: Next day I will be working on the #11815 task. Finish, start next task.

@enso-bot
Copy link

enso-bot bot commented Dec 19, 2024

Keziah Wesley reports a new STANDUP for yesterday (2024-12-18):

Progress: Still refactoring suggestion DB. It should be finished by 2024-12-20.

Next Day: Next day I will be working on the #11815 task. Finish, start next task.

kazcw added a commit that referenced this issue Dec 19, 2024
- `SuggestionUpdateProcessor` will simplify adding more contextual information
  to the update application process.
- Mock suggestion data is constructed using `lsUpdate` so that the mocking
  logic doesn't have to be kept consistent with the `lsUpdate` implementation.
- When uploading, use `ExternalId` to identify function; it's simpler than
  comparing stack items.
- Correct some language server definitions that can be `null` in practice.
- Add a test covering *current* behavior wrt. #11815; following PR will update
  expected results.
@enso-bot
Copy link

enso-bot bot commented Dec 20, 2024

Keziah Wesley reports a new STANDUP for yesterday (2024-12-19):

Progress: Split out some preparatory refactoring and PR'd. It should be finished by 2024-12-20.

Next Day: Next day I will be working on the #11815 task. Finish, start next task.

@enso-bot
Copy link

enso-bot bot commented Dec 24, 2024

Keziah Wesley reports a new STANDUP for the last Friday (2024-12-20):

Progress: Didn't end up getting much work done today It should be finished by 2024-12-20.

Next Day: Next day I will be working on the #11815 task. Finish, start next task.

kazcw added a commit that referenced this issue Jan 2, 2025
* Refactoring in preparation for normalized qualified names

- `SuggestionUpdateProcessor` will simplify adding more contextual information
  to the update application process.
- Mock suggestion data is constructed using `lsUpdate` so that the mocking
  logic doesn't have to be kept consistent with the `lsUpdate` implementation.
- When uploading, use `ExternalId` to identify function; it's simpler than
  comparing stack items.
- Correct some language server definitions that can be `null` in practice.
- Add a test covering *current* behavior wrt. #11815; following PR will update
  expected results.
@enso-bot
Copy link

enso-bot bot commented Jan 3, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-02):

Progress: Normalizing the suggestion DB data model; not strictly needed for this task but we have upcoming SDB changes that will benefit from it too. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Same task.

@enso-bot
Copy link

enso-bot bot commented Jan 6, 2025

Keziah Wesley reports a new STANDUP for the last Friday (2025-01-03):

Progress: Refactored suggestion DB to properly represent suggestion-type-specific data. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Now that the structure is in place, simplify how the LS data is mapped to the data we need.

@enso-bot
Copy link

enso-bot bot commented Jan 7, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-06):

Progress: Refactored mapping of LS data to app data. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Updating tests, integrating earlier QN WIP with structure refactor.

@enso-bot
Copy link

enso-bot bot commented Jan 9, 2025

Keziah Wesley reports a new STANDUP for the last Tuesday (2025-01-07):

Progress: Update lsUpdate tests, working on the various smaller tests. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Finishing

@enso-bot
Copy link

enso-bot bot commented Jan 9, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-08):

Progress: Generalizing types to allow items in top level of module It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Finishing

@enso-bot
Copy link

enso-bot bot commented Jan 10, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-09):

Progress: Working through test failures It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11815 task. Finishing

@enso-bot
Copy link

enso-bot bot commented Jan 13, 2025

Keziah Wesley reports a new STANDUP for the last Friday (2025-01-10):

Progress: Propagating type changes through computed values store / message pointers to the process boundary. It should be finished by 2025-01-18.

Next Day: Next day I will be working on the #11815 task. Finishing PR

@enso-bot
Copy link

enso-bot bot commented Jan 14, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-13):

Progress: Working on CV store, imports analysis changes It should be finished by 2025-01-18.

Next Day: Next day I will be working on the #11815 task. Finishing PR

@enso-bot
Copy link

enso-bot bot commented Jan 15, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-14):

Progress: Switching usages of LS types to parallel hierarchy of types with our normalizations It should be finished by 2025-01-18.

Next Day: Next day I will be working on the #11815 task. Finishing PR

@kazcw kazcw mentioned this issue Jan 16, 2025
5 tasks
@enso-bot
Copy link

enso-bot bot commented Jan 16, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-15):

Progress: Switching usages of LS types to parallel hierarchy of types with our normalizations; opened a PR covering SDB refactor It should be finished by 2025-01-18.

Next Day: Next day I will be working on the #11815 task. Finishing task

mergify bot pushed a commit that referenced this issue Jan 17, 2025
Allow different suggestion DB types to have different properties, instead of assigning placeholder values; move type-specific entry logic into entry definitions. The `Any` type is now implicit: It is no longer stored as a parent of every type. When filtering by self-type, `Any` is treated as unknown.

Part of #11815.
@enso-bot
Copy link

enso-bot bot commented Jan 17, 2025

Keziah Wesley reports a new STANDUP for yesterday (2025-01-16):

Progress: Switching to normalized types It should be finished by 2025-01-18.

Next Day: Next day I will be working on the #11815 task. Final PR of task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug -gui
Projects
Status: 🔧 Implementation
Development

No branches or pull requests

4 participants