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
Need to investigate whether this is worth the effort to do in the backend or if we should do this on the front end. It feels kind of like a convenience data point and would be 'repeating' data on the back end. I think question is whether or not specific permissions would be allowed on active vs inactive states on the server side. Such as modifying, retrieval, etc.
If we were to do it:
Projects should be marked off in the db as 'active' or 'inactive' with 'inactive' being if they are older than 15 days.
For now the only benefit is that the the app can filter and create views based on the state. Eventual benefit is we can have multiple states, be able to assign specific abilities to various states.
The text was updated successfully, but these errors were encountered:
#2 #4 are client side solutions to this problem.
Need to investigate whether this is worth the effort to do in the backend or if we should do this on the front end. It feels kind of like a convenience data point and would be 'repeating' data on the back end. I think question is whether or not specific permissions would be allowed on active vs inactive states on the server side. Such as modifying, retrieval, etc.
If we were to do it:
Projects should be marked off in the db as 'active' or 'inactive' with 'inactive' being if they are older than 15 days.
For now the only benefit is that the the app can filter and create views based on the state. Eventual benefit is we can have multiple states, be able to assign specific abilities to various states.
The text was updated successfully, but these errors were encountered: