Skip to content

@:jcustomwrite should be respected on abstracts. #93

Description

@EliteMasterEric

Here is an example of what I am trying to do:

typedef TypeToWrite = {
  var values:Array<EntrypointItem>
};

// This custom writer should be respected but is IGNORED for this abstract
@:jcustomwrite(package.Writers.writeEntrypointItem)
abstract EntrypointItem(Either<String, EntrypointObject>) from Either<String, EntrypointObject> to Either<String, EntrypointObject> {}

I want the values to be written, and parsed, as either a String or an EntrypointObject (which is a typical typedef), detecting what type it is.

There's also the problem that, when implementing writeEntrypointItem, there's no easy way to tell the writer to "write this object" instead of returning a string; you can JSON stringify the value you want to return, but that breaks the indentation of the file.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions