Skip to content

Conversation

@philnash
Copy link
Contributor

@philnash philnash commented Sep 4, 2024

This is a bit picky, but when I copied the example page.tsx from https://firebase.google.com/docs/genkit/nextjs I found I had some linter errors in my editor.

I have updated the example code to:

  • more closely match React style (varName and setVarName for useState)
  • reflect good practices in forms (using htmlFor for labels)

I also added some spacing to the button, to make it easier to see.

Checklist (if applicable):

  • [] N/A Tested (manually, unit tested, etc.)
  • [] N/A Changelog updated
  • Docs updated
@kevinthecheung
Copy link
Contributor

thank you!

@MichaelDoyle
Copy link
Member

MichaelDoyle commented Sep 16, 2024

@philnash looks like there is an issue w/ the build (unrelated to your change). can you rebase? I think it was resolved in another commit.

See also: #884

This is a bit picky, but when I copied the example page.tsx from https://firebase.google.com/docs/genkit/nextjs I found I had some linter errors in my editor.

I have updated the example code to:
* more closely match React style (varName and setVarName for useState)
* reflect good practices in forms (using htmlFor for labels)

I also added some spacing to the button, to make it easier to see.
@philnash philnash force-pushed the philnash-update-nextjs-starter-code branch from fc28c68 to 2c40c6a Compare September 17, 2024 00:23
@philnash
Copy link
Contributor Author

Thanks @MichaelDoyle, a rebase did fix it (at least the formatter was happy locally). I've pushed up the latest, but it needs permission to run the workflows again.

@MichaelDoyle MichaelDoyle merged commit 28ecb65 into firebase:main Sep 17, 2024
@philnash philnash deleted the philnash-update-nextjs-starter-code branch September 17, 2024 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants