Add Supported Fields Based on Registrar fields bit flags #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to the
identity-registrar
andIdentityForm
components to enhance the handling of supported identity fields and improve the form's flexibility and functionality.Enhancements to
identity-registrar
component:supportedFields
property toMainContentProps
to dynamically handle supported identity fields. [1] [2] [3] [4]getSupportedFields
function to determine supported fields based on a bitfield and updated theIdentityRegistrarComponent
to use this function.Enhancements to
IdentityForm
component:legal
,web
,matrix
,email
,discord
,twitter
,image
,github
, andpgp_fingerprint
, each with validation and transformation logic. [1] [2] [3]supportedFields
property. [1] [2]