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

[browser] move files around #92429

Closed
wants to merge 4 commits into from

Conversation

pavelsavara
Copy link
Member

@pavelsavara pavelsavara commented Sep 21, 2023

Introducing directories

  • core
  • jiterpreter
  • interop

and moving TS files into them.

@pavelsavara pavelsavara added arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm labels Sep 21, 2023
@pavelsavara pavelsavara added this to the 9.0.0 milestone Sep 21, 2023
@pavelsavara pavelsavara self-assigned this Sep 21, 2023
@ghost
Copy link

ghost commented Sep 21, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

null

Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript, os-browser

Milestone: 9.0.0

@campersau
Copy link
Contributor

I guess this is going to conflict with #91699

# Conflicts:
#	src/mono/wasm/runtime/core/http.ts
@pavelsavara
Copy link
Member Author

I guess this is going to conflict with #91699

It was not that bad :)

@pavelsavara pavelsavara marked this pull request as ready for review September 22, 2023 05:31
@maraf
Copy link
Member

maraf commented Sep 22, 2023

What about splitting the code by module?

  • runtime
    • diagnostics
    • jiterpreter
    • ...
  • loader
    • run.ts
    • ...
  • emscripten
    • dotnet.lib.js
    • dotnet.pre.js
    • ...

What about moving typescript/js code to a separate folde (like client/client-side)?

@pavelsavara
Copy link
Member Author

What about splitting the code by module?

That's exactly the idea, and we could do better than I did so far.

I did core for dotnet.runtime.js because I didn't like runtime/runtime folder. We could rename the outer folder.

Rename of es6 to emscripten is good idea, I forgot about that. But maybe we could do native instead.

@pavelsavara
Copy link
Member Author

I need to work on something else ... maybe later

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants