Trigger a StreamController at ngOnInit()












0















Taking this example from the doc:



Stream<List<Hero>> heroes;
// ···
void ngOnInit() async {
heroes = _searchTerms.stream
.transform(debounce(Duration(milliseconds: 300)))
.distinct()
.transform(switchMap((term) => term.isEmpty
? Stream<List<Hero>>.fromIterable([<Hero>])
: _heroSearchService.search(term).asStream()))
.handleError((e) {
print(e); // for demo purposes only
});
}


Say I want to "trigger" the stream at ngOnInit().



After some tests, I find this can be done by calling void search(String term) => _searchTerms.add(term); just after this:



await Future.delayed(Duration(milliseconds: 1));


Seems that the _searchTerms call inside ngOnInit() is not await.



Could anyone explain why this works that way, or what I am doing wrong?










share|improve this question



























    0















    Taking this example from the doc:



    Stream<List<Hero>> heroes;
    // ···
    void ngOnInit() async {
    heroes = _searchTerms.stream
    .transform(debounce(Duration(milliseconds: 300)))
    .distinct()
    .transform(switchMap((term) => term.isEmpty
    ? Stream<List<Hero>>.fromIterable([<Hero>])
    : _heroSearchService.search(term).asStream()))
    .handleError((e) {
    print(e); // for demo purposes only
    });
    }


    Say I want to "trigger" the stream at ngOnInit().



    After some tests, I find this can be done by calling void search(String term) => _searchTerms.add(term); just after this:



    await Future.delayed(Duration(milliseconds: 1));


    Seems that the _searchTerms call inside ngOnInit() is not await.



    Could anyone explain why this works that way, or what I am doing wrong?










    share|improve this question

























      0












      0








      0








      Taking this example from the doc:



      Stream<List<Hero>> heroes;
      // ···
      void ngOnInit() async {
      heroes = _searchTerms.stream
      .transform(debounce(Duration(milliseconds: 300)))
      .distinct()
      .transform(switchMap((term) => term.isEmpty
      ? Stream<List<Hero>>.fromIterable([<Hero>])
      : _heroSearchService.search(term).asStream()))
      .handleError((e) {
      print(e); // for demo purposes only
      });
      }


      Say I want to "trigger" the stream at ngOnInit().



      After some tests, I find this can be done by calling void search(String term) => _searchTerms.add(term); just after this:



      await Future.delayed(Duration(milliseconds: 1));


      Seems that the _searchTerms call inside ngOnInit() is not await.



      Could anyone explain why this works that way, or what I am doing wrong?










      share|improve this question














      Taking this example from the doc:



      Stream<List<Hero>> heroes;
      // ···
      void ngOnInit() async {
      heroes = _searchTerms.stream
      .transform(debounce(Duration(milliseconds: 300)))
      .distinct()
      .transform(switchMap((term) => term.isEmpty
      ? Stream<List<Hero>>.fromIterable([<Hero>])
      : _heroSearchService.search(term).asStream()))
      .handleError((e) {
      print(e); // for demo purposes only
      });
      }


      Say I want to "trigger" the stream at ngOnInit().



      After some tests, I find this can be done by calling void search(String term) => _searchTerms.add(term); just after this:



      await Future.delayed(Duration(milliseconds: 1));


      Seems that the _searchTerms call inside ngOnInit() is not await.



      Could anyone explain why this works that way, or what I am doing wrong?







      dart angular-dart dart-html






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 24 '18 at 19:19







      user8773215































          1 Answer
          1






          active

          oldest

          votes


















          0














          It isn't exactly clear what you are trying to do here, but some background that might help.



          Angular lifecycle methods can't be interrupted. They also will not wait for async actions. They are simply callbacks that will be called at the point of the angular lifecycle. Asking angular to wait for you to do work at some unknown point to it is not possible. What if the action never completed? What happens to the rest of the subtree? You would be in some weird state that would invalidate much of the logic and the app.



          Instead we use change detection/variables to change the state of the component to handle these async actions. So you could show a progress indicator using a boolean variable until the rpc comes back and then show the results by flipping the variable.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52976463%2ftrigger-a-streamcontroller-at-ngoninit%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown
























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It isn't exactly clear what you are trying to do here, but some background that might help.



            Angular lifecycle methods can't be interrupted. They also will not wait for async actions. They are simply callbacks that will be called at the point of the angular lifecycle. Asking angular to wait for you to do work at some unknown point to it is not possible. What if the action never completed? What happens to the rest of the subtree? You would be in some weird state that would invalidate much of the logic and the app.



            Instead we use change detection/variables to change the state of the component to handle these async actions. So you could show a progress indicator using a boolean variable until the rpc comes back and then show the results by flipping the variable.






            share|improve this answer




























              0














              It isn't exactly clear what you are trying to do here, but some background that might help.



              Angular lifecycle methods can't be interrupted. They also will not wait for async actions. They are simply callbacks that will be called at the point of the angular lifecycle. Asking angular to wait for you to do work at some unknown point to it is not possible. What if the action never completed? What happens to the rest of the subtree? You would be in some weird state that would invalidate much of the logic and the app.



              Instead we use change detection/variables to change the state of the component to handle these async actions. So you could show a progress indicator using a boolean variable until the rpc comes back and then show the results by flipping the variable.






              share|improve this answer


























                0












                0








                0







                It isn't exactly clear what you are trying to do here, but some background that might help.



                Angular lifecycle methods can't be interrupted. They also will not wait for async actions. They are simply callbacks that will be called at the point of the angular lifecycle. Asking angular to wait for you to do work at some unknown point to it is not possible. What if the action never completed? What happens to the rest of the subtree? You would be in some weird state that would invalidate much of the logic and the app.



                Instead we use change detection/variables to change the state of the component to handle these async actions. So you could show a progress indicator using a boolean variable until the rpc comes back and then show the results by flipping the variable.






                share|improve this answer













                It isn't exactly clear what you are trying to do here, but some background that might help.



                Angular lifecycle methods can't be interrupted. They also will not wait for async actions. They are simply callbacks that will be called at the point of the angular lifecycle. Asking angular to wait for you to do work at some unknown point to it is not possible. What if the action never completed? What happens to the rest of the subtree? You would be in some weird state that would invalidate much of the logic and the app.



                Instead we use change detection/variables to change the state of the component to handle these async actions. So you could show a progress indicator using a boolean variable until the rpc comes back and then show the results by flipping the variable.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 3:54









                Ted SanderTed Sander

                1,24127




                1,24127






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52976463%2ftrigger-a-streamcontroller-at-ngoninit%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Full-time equivalent

                    Bicuculline

                    さくらももこ