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

Eagle 1039 #616

Open
wants to merge 445 commits into
base: master
Choose a base branch
from
Open

Eagle 1039 #616

wants to merge 445 commits into from

Conversation

james-strauss-uwa
Copy link
Collaborator

Could you take a quick look at this. Sorry, its a large code change.

The major changes are to use a common interface (a modal previously used for displaying/fixing graph errors) for three purposes:

  1. Displaying/Fixing graph errors
  2. Displaying/Fixing errors during loading of palettes and graphs
  3. Displaying/Performing updates to components based on newer palette definitions

It's useful to enable the following settings:

  • Show edge/node errors/warnings in inspector: Warnings
  • Show File Loading Warnings: Enabled

And test:

  • Loading graphs and palettes, clicking "Show", "Fix" buttons on single issues, and "FixAll" button on the modal
  • Fixing a graph with errors (again use "Show", "Fix" and "Fix All")
  • Updating a graph (for example the graph in the EAGLE repo in tests/data/component-update-test.graph)

Also please check that removing line 345 from src/Setting.ts is OK

@M-Wicenec
Copy link
Collaborator

Removing that setting is fine, that was my mistake

the fix all and individual fixing of issues in the modal on load are working great.

Problems:
the individual fixing of issues in the inspector was not doing anything for me, both for nodes in the palette and nodes in the graph

there is no way to get back to the version of the error modal that displays both, errors in the graph and in the palettes.
maybe we should have both available in the normal error modal with tabs to switch between graph and palette at the top?

james-strauss-uwa and others added 30 commits March 20, 2024 11:40
Remove the requirement for a 'dropclass' field on Constructs
Default value of settings were not reset for 'Student' or 'Component' mode
Make it hard to save a graph with no name (or a bad name)
Removed the 'Description' category from CategoryData.
Factored out some common validation code into a single function within Utils
…do function from taking users back to a previously loaded graph.
…lass of edges that can never be created, even if the user has set 'allow invalid edges' to true.
…ments etc. We don't want the fix function to delete all these, we should rely on the user to switch them input PythonApps
Add new 'Impossible' value to the Eagle.LinkValid enum
removed all d3 stuff except in npm node modules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants