trader | ping pong and maker/taker order bot | Cryptography library

Your Delete logic seems fine. What I would look at in more detail is your Edit.

Overall I am not a fan of ever passing Entities between the server and the view, especially accepting an entity from the view. This is generally a bad practice because you are trusting the data coming from the view, which can easily be tampered with. The same when passing data from a view to server, this can lead to accidentally exposing more information about your domain (and performance issues) just by having some "sloppy" JavaScript or such converting the model into a JSON model to inspect client-side. The recent case of the journalist being accused of "hacking" because they found extra information via the browser debugger in a Missouri government website outlines the kind of nonsense that can come up when server-side code has the potential to send far too much detail to a browser.

In any case, in your Edit method when you accept the bound Product after deactivating the Discontinued flag, what values are in that Entity model? For instance if you use Delete to set Discontinued to "True", then go to the Edit view for that product and un-check that input control and submit the form, in your "product" coming in the Edit page, what is the state of the product.Discontinued?

If the value is still "True" then there is a potential problem with your page binding where the EditorFor is not linking to that flag properly or the value is not deserializing into the Product entity. (a private or missing setter?)

If it is coming back with what should be the correct value, then I would look at changing how you update entities. Code like this:

All I had to change was in my Program.cs

After the rest of the day searching for the answer it was the most simple but not the wisest solution that worked:

Completely ignored the .npmrc file and in package.json under dependencies just added the personal access token like so: @github.com

First, you can directly access the dictionary fields as members of the Quote objects - i.e. you can just do q.ask_price to get the price from the received Quotes.

In your quote_callback function you get every Quote object as an argument. So, if you always only want to access the last received Quote object which has symbol = "HB", you could define a global dictionary named e.g. quotes which will contain one key == symbol and value == last Quote with that symbol per symbol type.

Now, in get_quote you can use a simple dictionary lookup for the desired key in the quotes dictionary. In the end, you need to repeatedly call get_quote until a quote object with the desired symbol value is received. The whole code could look like this:

I found the correct differentiable code for the loss function i wanted to use.

Great question Josiah, there is a lot going on here:

• You probably already discovered this, but the beginMonth test in the code sample above, as written, will only flag the first day of the first full month that is in your allowed date range. We'll fix that below.
• There are some related changes in Pine v5 to how colors are set, and from v4 as to how variables are declared and updated, so I have leveraged those below as well.
• You have two tests going on: timeframe and doji-ness, so I've split them up below for clarity.

This was a great example to work with because it highlights a problem I often have in my own Pine scripting, looking for opportunities or conditions:

Why don't I see any opportunities flagged by my rules? Is there something wrong with my code? Did it even run? Or is it the data I'm looking at, in there just aren't any matching candles, but the code is fine? (Oh, and am I reading the wrong version of the documentation, using the correct version of the function, updating the values on each bar or not...)

Even when we succeed in crafting the correct tests and succeed in combining them properly, it's still very hard to effectively plot dojis. Partly because they're rare, and partly because of what they look like on a chart. That also makes it hard to tell if our code is working, even when it is.

So I try to make sure my code helps me see just what's going wrong and what isn't. And hopefully this example is useful to others on that level as well.

The code below should do what you want. To answer your headline question, it uses a variable called okayToPlot to limit rendering of your indicator to just days in the past N months.

It also shows how find and effectively highlight doji's, so you don't go insane trying to see a thin black line that was rendered on top of another thin black line.

I used overlay=false to help you (okay, me) get a better look at what was going on. Once you're satisfied with your working script, just change it back to overlay=true and you're good to go.

If you copy/paste this into your Pine Editor as a new Indicator and try it out on a daily chart for some slow-moving large cap stock, you should spot a doji if you scan a long enough period.

I used 8 months on BCE on the TSX in late 2021 and it finds 2 days with a doji formation, which it highlights with a yellow background and a bright green + sign.

You are missing a class that matches the list of Species that your JSON contains:

Link need prop to="where to go", if you want to go nowhere just use to="#"