Skip to content

WIP: Where to place the (php) transpilation results? #5

@mhsdesign

Description

@mhsdesign

WIP: ... need to shutdown my pc ;) see you soon

The idea seems that this package PackageFactory.ComponentEngine is framework agnostic an should even work with plain php (composer).

If the files should be generated via CLI command, then one needs a flow adapter package already which provides the Cli controller.
Or we use a composer bin executable or something the like which would work cross framework too.

Multiple Exports per file

Transpile in current package (and relative includes)

Just make sure psr is correctly configured and lets goo place the files ;)

Import from other (composer) packages:

  • Option A: Each package needs to provide its own transpliled files

    • Pro: save complex option B
    • Con: if package only ships php transpilation but not fusion or typescript, one is out of luck
    • Pro: phpstan would work on ci without pre compile
      ´
  • Options B: On transplile, also handle 3rd party packages

    • If we assume that one is using composer, then we could leverage the existing packages folders and configured psr-4 autoloading and just dump the php files into the via composer installed packages.

if we want to transpile to neos fusion we would need to add a flow adapter package i guess....

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions