- Sort Score
- Num 10 results
- Language All
Results 401 - 410 of 486 for Comments (0.04 seconds)
-
LICENSES/vendor/cel.dev/expr/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Nov 06 20:53:17 GMT 2024 - 11.2K bytes - Click Count (0) -
LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Wed Feb 22 18:59:39 GMT 2023 - 11.1K bytes - Click Count (0) -
docs/fr/docs/tutorial/security/simple-oauth2.md
Le seul détail manquant est qu'il n'est pas encore réellement « sécurisé ».
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:37:13 GMT 2026 - 11.2K bytes - Click Count (0) -
LICENSE
boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Thu Apr 02 15:34:12 GMT 2026 - Last Modified: Thu Jun 14 07:45:22 GMT 2018 - 11.1K bytes - Click Count (0) -
LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Tue Nov 22 19:44:46 GMT 2016 - 11.1K bytes - Click Count (0) -
LICENSES/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.3K bytes - Click Count (0) -
LICENSES/vendor/github.com/NYTimes/gziphandler/LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Feb 03 21:57:36 GMT 2021 - 11.2K bytes - Click Count (0) -
LICENSE
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Fri Apr 03 20:58:12 GMT 2026 - Last Modified: Fri Apr 18 13:54:00 GMT 2025 - 11.1K bytes - Click Count (0) -
apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt
boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Tue Jan 28 11:47:17 GMT 2020 - 11.1K bytes - Click Count (0) -
internal/config/identity/plugin/config.go
Key: RoleID, Description: "unique ID to generate the ARN" + defaultHelpPostfix(RoleID), Optional: true, Type: "string", }, config.HelpKV{ Key: config.Comment, Description: config.DefaultComment, Optional: true, Type: "sentence", }, } ) // Allows only Base64 URL encoding characters.
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 13.3K bytes - Click Count (0)