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
Presently, the way we render audits are tightly coupled to implementation details within our application. This became apparent when we worked on PRs that involved renaming some columns:
We'd like to explore alternative rendering options for the audits and align on determine which details are important to display and what should be hidden.
Describe the solution you'd like
In an ideal state, audits should be decoupled from application logic.
Once we align on an approach for rendering audits, we'll need to revisit the decision to maintain legacy fields. It's possible we may need to remove the mfa_seed field from UserResource.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Presently, the way we render audits are tightly coupled to implementation details within our application. This became apparent when we worked on PRs that involved renaming some columns:
We'd like to explore alternative rendering options for the audits and align on determine which details are important to display and what should be hidden.
Describe the solution you'd like
In an ideal state, audits should be decoupled from application logic.
Describe alternatives you've considered
See discussion for some proposed options.
Additional context
Once we align on an approach for rendering audits, we'll need to revisit the decision to maintain legacy fields. It's possible we may need to remove the
mfa_seed
field fromUserResource
.The text was updated successfully, but these errors were encountered: