-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
community: add spanish translation for SECURITY.mx (fix #5851) #5884
base: master
Are you sure you want to change the base?
Conversation
Beep boop! 🤖 Hey @ErickJoestar, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
translations/SECURITY.mx_spanish.md
Outdated
|
||
### ¿Cuando NO deberia reportar una vulnerabilidad? | ||
|
||
- Necesitas ayuda afinando los componentes de seguridad en el moto de Hasura GraphQL . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hola, revisaba tu PR y vi que tienes un typo, debería de ser motor de Hasura GraphQL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arreglado
translations/SECURITY.mx_spanish.md
Outdated
|
||
## Tiempo de divulgación publica | ||
|
||
La fecha para la divulgación pública es negociada por el equipo de seguridad Hasura y la persona que reportó el problema. Preferimos hacer una divulgación pública tan pronto como una mitigación para el problema esté disponible. Es razonable retrasar la divulgacion cuando un problema o solución no está totalmente entendida, la solución no está bien probada, o lista para la coordinación de proveedores. El periodo de tiempo para la divulgación es desde inmediato (especialmente si ya es conocido públicamente) hasta unas semanas. Esperamos que el periodo de tiempo entre un reporte y una divulgación pública esté disponible en 7 días. Los mantenedores del motoro de Hasura GraphQL y el equipo de seguridad tomarán la llamada final en poner una fecha de divulgación. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aquí faltaría un conector en es negociada por el equipo de seguridad de Hasura
y también cambiar motoro a motor
Deploy preview for hasura-docs ready! Built with commit c270bdb |
Description
Added doc translations for spanish in SECURITY.mx
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-required
label.Affected components
Related Issues
fix #5851
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed