Corrected Generation Of Entity Relationship Diagram

[tslever]

Specifically, I corrected inverted relationships following Christophe's comment on 08/05/2024 11:31:34Z at https://stackoverflow.com/questions/78776709/drawing-relationships-in-entity-relationship-diagram/78831819?noredirect=1#comment138990567_78831819.

Before I made these changes an Entity Relationship Diagram was

After I made these changes an Entity Relationship Diagram was

[tslever]

@R0tenur , hopefully changes relating to creating our vsix file on Linux will satisfy your Continuous Integration. Hopefully changes to docs/docs.md will address your concerns.

I restored documentation relating to using yarn to create our vsix file.

I restored your sections on debugging and using your front end.

docs/docs.md is no longer Windows specific.

[tslever]

@R0tenur , you can see a passing GitHub action at https://github.com/tslever/Generator_Of_ERDs/actions .

[tslever]

@R0tenur , I have deleted files named package-lock.json.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[andreasmarxer]

First thanks for this fix and update!

I would be really interested in this correction of the directions, but after updating from V0.9.1 to the latest version V0.9.4 I receive an error and the diagram generation is not anymore working: Error loading webview: Error: Could not register service worker: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state..

@R0tenur @tslever

Anyone also experiencing this with v0.9.4 or any ideas what could be the issue on my side?

[tslever]

@andreasmarxer , hi. You're welcome. Thanks to @R0tenur also. I am able to generate an ERD. See ./docs/docs.md. I again cloned this repository, regenerated the extension using Git Bash and npm, and reinstalled the extension. I recall ensuring Continuous Integration using Windows Subsystem for Linux and the GitHub Action of my fork of this repository. Before regenerating the extension, to avoid experiencing dependency hell again, I downloaded the package-lock.json files that I deleted toward the end of my work per @R0tenur's request.

[andreasmarxer]

Hi @tslever Thanks for the reply and sorry for the misunderstanding.

I did not build the visx package by my own, I did jsut take the latest version v0.9.4 available in the builds, which should include this change as well. But I will in this case give it a try to generate the visx package locally on my machine.

[tslever]

@andreasmarxer , I noticed that this pull request is closed. Would you please create a pull request with a new build available in the appropriate location?