Clear / Clean / Delete angularJS $location.search()

Bresleveloper's AngularJS tutorial:  $location.search() :)

i tried a few thing but the only thing that worked was 
for (prop in $location.search()) 
        $location.search(prop, null);


Comments

  1. BresleveloperNovember 3, 2015 at 8:21 AM

    Thank you, its really my agenda in this blog to bring simple tutorials with simple enough code to grab the issue

    ReplyDelete
  2. rah=jivJanuary 15, 2017 at 10:37 AM

    This comment has been removed by the author.

    ReplyDelete
  3. anirudhMay 17, 2019 at 2:33 PM



    The information which you have provided is very good. It is very useful who is looking for Best Devops Training Institute

    ReplyDelete
  4. vijayJuly 26, 2020 at 2:40 PM

    This article is really helpful for me. I am regular visitor to this blog. Share such kind of article more in future. Personally i like this article Really awesome..
    Salesforce Training in Chennai

    Salesforce Online Training in Chennai

    Salesforce Training in Bangalore

    Salesforce Training in Hyderabad

    Salesforce training in ameerpet

    Salesforce Training in Pune

    Salesforce Online Training

    Salesforce Training

    ReplyDelete
  5. vedanta hospitalMay 5, 2025 at 12:17 PM

    This comment has been removed by the author.

    ReplyDelete
  6. kalyanibrolly02May 13, 2025 at 4:12 PM

    Great solution! Using the loop to clear out the query parameters in $location.search() is a clean and effective approach. It’s always helpful to find these little tricks to keep the URL parameters manageable in AngularJS applications. Thanks for sharing this. Looking forward to more insightful posts like this.Looking to master the world of digital marketing? We provide comprehensive digital marketing courses that equip you with the skills to succeed in today's fast-paced online landscape AI Powered Digital Marketing Course In Hyderabad.

    ReplyDelete

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

SPFx with Angular, Full tutorial

 White you can use the pnp-generator , I really wanted to created this kind of solution all by myself, since I also wanted to implement it with SP-2019, with SFPx 1.4.x Part 1: Setup I started with a clean machine, installed LTS node 14.17.0 , and installed latest gulp, yo, sp-generator for yo, and angular-cli command: npm install gulp yo @microsoft/generator-sharepoint --global results: + gulp@4.0.2 + yo@4.2.0 + @microsoft/generator-sharepoint@1.12.1 command: npm install -g @angular/cli results: + @angular/cli@12.0.2 *NOTE - To the time of writing, I had an error generating browser application bundles so I downgraded to angular 10.x, and re-create the project npm uninstall -g @angular/cli npm cache clean --force npm install -g @angular/cli@10.2.0 And so our journey begins! Create new Ng project ng new ng-for-spfx-ex Create new SPFx WebPart Project - just  yo Part 2: Test NG with SPFx Within the  angular.json   file lets change the output path, I've made 1 folde...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more