…omponent schema

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name besed on the postcode nd husenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
somthing goes wrong with the API call.

… and preview in the builder according to autoPopulated field

…nually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name besed on the postcode nd housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required.

… and preview in the builder according to autoPopulated field

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required. Additionally,
the postcode and housenumber fields are always both required or none.

…eetname and city

Updated street name and city serializer fields in order to be able to
require these fields in case the component is required.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.

…ually fill in city and streetname

Until now the addressNL component would retrieve the city and street
name based on the postcode and housenumber. These fields were always
read-only but now we want to be able to fill in city and street name if
something goes wrong with the API call.