chore: no magic strings #34

Merged
BenjaminPalko merged 2 commits from paraglider-no-magic-strings into master 2024-12-30 17:29:47 -05:00
BenjaminPalko commented 2024-12-24 15:02:13 -05:00 (Migrated from github.com)
No description provided.
DanMihailescu (Migrated from github.com) reviewed 2024-12-24 15:02:13 -05:00
piopi (Migrated from github.com) reviewed 2024-12-24 15:57:52 -05:00
piopi (Migrated from github.com) left a comment

Don't think you should use translation for API errors

Don't think you should use translation for API errors
BenjaminPalko commented 2024-12-27 17:33:33 -05:00 (Migrated from github.com)

Don't think you should use translation for API errors

They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense?

> Don't think you should use translation for API errors They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense?
piopi commented 2024-12-28 10:07:41 -05:00 (Migrated from github.com)

Don't think you should use translation for API errors

They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense?

It makes sense, I like that way!

> > Don't think you should use translation for API errors > > They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense? It makes sense, I like that way!
BenjaminPalko commented 2024-12-30 12:37:28 -05:00 (Migrated from github.com)

Don't think you should use translation for API errors

They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense?

It makes sense, I like that way!

Opened #35 for this work, its a bit more involved than what Im doing here since we need a system for passing errors from the backend to the frontend + form needs to properly handle error states

> > > Don't think you should use translation for API errors > > > > > > They are form errors, we could return a flag from the server then serve the message on the client. Its an extra step, but does that make sense? > > It makes sense, I like that way! Opened #35 for this work, its a bit more involved than what Im doing here since we need a system for passing errors from the backend to the frontend + form needs to properly handle error states
piopi commented 2024-12-30 12:43:35 -05:00 (Migrated from github.com)

@BenjaminPalko Can you remove please the translation from the api 🙏🏽

@BenjaminPalko Can you remove please the translation from the api 🙏🏽
piopi (Migrated from github.com) approved these changes 2024-12-30 15:10:00 -05:00
Sign in to join this conversation.
No description provided.