Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^2: Problems with Newest Nodes

by roho (Chancellor)
on Jun 15, 2021 at 04:37 UTC ( #11133879=note: print w/replies, xml ) Need Help??


in reply to Re: Problems with Newest Nodes
in thread Problems with Newest Nodes

Hmmm - somehow that doesn't seem quite right - what is the procedure to request a change to PerlMonks to allow this to be changed back? I feel like Alice when she fell down the rabbit hole.

"It's not how hard you work, it's how much you get done."

Replies are listed 'Best First'.
Re^3: Problems with Newest Nodes
by cavac (Priest) on Jun 15, 2021 at 08:32 UTC

    what is the procedure to request a change to PerlMonks

    Technically, your first step would be to come up with a use case and discuss it in the Chatterbox and possibly here in PM Discussions.

    If your case has good arguments and other monks mostly agree that this would be a good thing to change, a PmDev has to decide if your request is technically possible (the PM backend is quite different than your average this-is-my-dog-forum).

    After that, your request will probably land on the Todo list, until someone implements it or not.

    I'm the most junior PmDev, only got promoted last week and i'm still reading the docs and the code. From what i could glean in a quick code search, it should be possible to implement a one level "undo" function. I'd be willing to invest the time since i had the same problem before (and this seems to be a good first project). But before i do anything, i'll have to check with my mentor.

    perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
      > it should be possible to implement a one level "undo" function.

      If you really want to invest into this° , I'd suggest just permanently storing the result of the numdays dialog˛ into the "lastChecked or so" -field

      because for a real undo you'd need a new field in the DB.

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery

      °) for training purposes sounds OK

      ˛) see Re: Problems with Newest Nodes

        Figured as much. Instead of blinking the field, mark it as invalid, like adding a '#' comment sign in front of it. I presume "Newest Nodes" is the only form that uses the field and the backend treats it as a text field?

        perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
      Thank you for your response cavac. The use case is pretty much what I stated in the OP. I would add that this change would prevent others from inadvertently making the same mistake I made and finding themselves in the same quandary. This has made me a little gun-shy about exploring other areas of the Monastery and wondering what other unpleasant surprises may await me.

      "It's not how hard you work, it's how much you get done."

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11133879]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (4)
As of 2022-01-26 20:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:












    Results (70 votes). Check out past polls.

    Notices?