Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change order of input fields for nuremberg administration backend #1747

Open
dkehne opened this issue Nov 5, 2024 · 4 comments
Open

Change order of input fields for nuremberg administration backend #1747

dkehne opened this issue Nov 5, 2024 · 4 comments
Labels

Comments

@dkehne
Copy link

dkehne commented Nov 5, 2024

The city of Nuremberg would like to swap the line with the expiration date and the start date in the position. The start date should be on the second line and the expiration date on the third line.

The reason for this is that the current arrangement is confusing for processing, as these dates are entered in the Nuremberg passport program in exactly the opposite order (first start then expiration date).

image001

@f1sh1918
Copy link
Contributor

f1sh1918 commented Nov 5, 2024

that is more difficult than it looks like @dkehne, since we have 2 manually rendered fields (name and ablaufdatum) and then the array of extensions (the rest)
now we would have to render sth in between the extensions
But we might adjust the extension structure and add a order param that sets flex order

@steffenkleinle
Copy link
Member

that is more difficult than it looks like @dkehne, since we have 2 manually rendered fields (name and ablaufdatum) and then the array of extensions (the rest)
now we would have to render sth in between the extensions
But we might adjust the extension structure and add a order param that sets flex order

Perhaps it would be easier to just make both name and expiration date extensions as well. Then we have uniform structure and can just order everything in the way we want to. Would perhaps even simplify logic in some parts.

@f1sh1918
Copy link
Contributor

f1sh1918 commented Nov 6, 2024

Yes but i wouldn't name this "extension" since its not

@steffenkleinle
Copy link
Member

Yes but i wouldn't name this "extension" since its not

Just fields/cardFields would perhaps make more sense, you are right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

3 participants