Not exactly. Disabling or enabling the prune is actually handled correctly. I thought about changing size of pruned blocks without redownloading everything. Changing pruning to lower value is easy, the client will just remove some blocks. But increasing it is difficult, because you have to redownload the whole chain even when you just need 2 GB more blocks when actually keeping last 50 GB.
Whenever you change your n parameter for prune=n, your Bitcoin Core will ask you to restart it with the message "Client restart required to activate changes".
In
Pros and Cons of Bitcoin Node types (Full node and Prune node), I advice to set up the n parameter around 99 GB. That threshold tested by some others and personally, from the data and chart of bitcoin blockchain size, I felt that 100 GB is good enough for the one who want to run prune node.
With 100 GB, in average rate of blockchain size increases annually, they will be able to store the blockchain transactions within past two years. As always, if you don't have issues with data capacity, let's set up and run your Full node.
And if you don't have anything to do in-depth technically, I think using SPV wallets, such as Electrum is not too bad option.