You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, we have way too many and badly-named IOfs functions, which just results in absolute chaos.
The upcoming, temporary solution will be to just put all of these into IOfsV1{} (or something alike). (Not IOfs{}!)
Step 2 will be to refactor all IOfs functions (names, parameters, results) so we get an unique system and put them into IOfsV2{} = IOfs. At this point we might think about keeping IOfsV1, maybe in a separate file, for now.
Step 3 will be to refactor all IOfs functions internally, which presumably won't change names, parameters or results, but may add to them. Step 3 may be delayed for good.
Step 4 will be to move from IOfsV2{} to just IOfs{} and remove IOfsV1{} completely. At this point, the existing functions shouldn't break anymore, but Step 4 should probably be reconsidered, also since we may likely eventually upgrade to IOfsV3 (or it may be necessary to go to IOfsV2_1) or something. IOfsV3 would probably change the storage system from localStorage to something bigger and better.
The text was updated successfully, but these errors were encountered:
We now have IOfs{} (I think it's IOfsv2{}). It's better than what we had before, and it's working pretty great. Could probably use some optimisations though.
Please use the new IOfsv2 (?) functions. Thank you!
At this point, we have way too many and badly-named IOfs functions, which just results in absolute chaos.
The upcoming, temporary solution will be to just put all of these into IOfsV1{} (or something alike). (Not
IOfs{}
!)Step 2 will be to refactor all IOfs functions (names, parameters, results) so we get an unique system and put them into
IOfsV2{} = IOfs
. At this point we might think about keeping IOfsV1, maybe in a separate file, for now.Step 3 will be to refactor all IOfs functions internally, which presumably won't change names, parameters or results, but may add to them. Step 3 may be delayed for good.
Step 4 will be to move from
IOfsV2{}
to justIOfs{}
and removeIOfsV1{}
completely. At this point, the existing functions shouldn't break anymore, but Step 4 should probably be reconsidered, also since we may likely eventually upgrade toIOfsV3
(or it may be necessary to go toIOfsV2_1
) or something. IOfsV3 would probably change the storage system from localStorage to something bigger and better.The text was updated successfully, but these errors were encountered: