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

improve the usability of some editors #1206

Open
wants to merge 3 commits into
base: maintenance/mps20232
Choose a base branch
from

Conversation

alexanderpann
Copy link
Member

The goal of this PR is to improve the usability of editors. All aliases cells should support code completion e.g. the word "enum" in an enum declaration and all keywords should have the right color. This must be done for all editors where there is more then one editor cell. For single cells the code completion menu works by default.

In addition, I fixed the issue with string types vs string types with constraints which broken model checking in a few editors.

@alexanderpann alexanderpann added the PRIO Use for issues/PRs with customer project background label Feb 4, 2025
@alexanderpann alexanderpann force-pushed the bugfix/code_completion_menus branch from 3d254f4 to 36a688d Compare February 4, 2025 08:54
Copy link
Member

@HeikoBecker HeikoBecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have already discussed tye type system question in private messages.
Here are some findings on the editors:

  • This editor diff looks strange. Might be worth double-checking:
    image
  • Potential typo: execution _c_ode vs execution _m_ode
    image
  • I did not see code influencing this part, but we might want to fix this editor bug as well:
    image

@alexanderpann alexanderpann force-pushed the bugfix/code_completion_menus branch from 36a688d to d4d86f8 Compare February 5, 2025 11:55
@alexanderpann
Copy link
Member Author

This editor diff looks strange.

I noticed it as well but it is correct.

Potential typo
Fixed.

The last issue is unrelated to my changes. I created a ticket for it: #1210

Copy link
Member

@HeikoBecker HeikoBecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for addressing my nitpicks and for improving the editors!

Please wait for the review of @arimer before merging this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PRIO Use for issues/PRs with customer project background
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants