Skip to content

idiomatic Aurelia #465

Description

@baerrach

I'm submitting a feature request

Current behavior:

While Aurelia tries to get out of your way, some of the concepts are "magical" to new frontend developers.

Expected/desired behavior:

  • What is the expected behavior?
    As part of the documentation it would be helpful to explain how you would do something without Aurelia, and then to show how Aurelia helps you do that.

  • What is the motivation / use case for changing the behavior?
    I have no idea if this course is free, https://egghead.io/lessons/javascript-redux-updating-the-state-with-the-fetched-data but it shows how you can write your own Redux implementation, and the reasoning behind the steps to get there.

I think this would also be useful for Aurelia.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions