Skip to content

request for new angular4 release #118

@ctaepper

Description

@ctaepper

there is a bug fixed in master #83 but not published to npm yet. we are currently workarounding this in a very ugly way. i am concerned, that with the upcoming release of the angular5 version #115 the bug won't be published to angular4 version anymore.

can you please give me some kind of info, if and when I can expect this bug to be published to angular-4.x version?

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