Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

@AfterViews execution order #553

Copy link
Copy link
@EurigJones

Description

@EurigJones
Issue body actions

I have a fragment class (A) and a parent fragment class (B). Both with @Afterviews methods.

The code generated always executes the method in A, before B. I would have thought that you'd generally want to execute the parent class code before it's child (but of course, not always)

Is there a way to define execution order?

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.