例文を組み込んだAlfred Workflowを作りました: Alfred Git Commit Message Example
以下転載:
import Foundation | |
// MARK: - Protocol | |
public protocol Notifier { | |
associatedtype Notification: RawRepresentable | |
} | |
public extension Notifier where Notification.RawValue == String { | |
以下転載:
// known-good: Swift 4, in Xcode Version 9.0 beta 2 (9M137d) | |
// will be unnecessary once the language can auto-synthesize for this case, or | |
// when Apple's ships a Codable implementation for CoreGraphics struct types. | |
extension CGSize : Codable { | |
enum CodingKeys: String, CodingKey { | |
case width | |
case height | |
} |
import Foundation | |
import KeychainAccess //https://github.com/kishikawakatsumi/KeychainAccess | |
import Firebase | |
//Requires shared Keychain with the same group name | |
class ApplicationBuilder { | |
enum Target { | |
case app |
import Foundation | |
struct Partial<Wrapped>: CustomStringConvertible, CustomDebugStringConvertible { | |
enum Error<ValueType>: Swift.Error { | |
case missingKey(KeyPath<Wrapped, ValueType>) | |
case invalidValueType(key: KeyPath<Wrapped, ValueType>, actualValue: Any) | |
} | |
private var values: [PartialKeyPath<Wrapped>: Any?] = [:] |
import Combine | |
import FirebaseAuth | |
public struct CombineAuth { | |
fileprivate let auth: Auth | |
} | |
extension CombineAuth { | |
public enum Error: Swift.Error { |
これは私が支援先に提供した、1 on 1 に関するノウハウや、思いを述べたドキュメントを元にしています。企業の枠を超えて共有したいことが多いので、ここに貼ります。
/** | |
* Temporary wrapper for firebase functions until @sentry/serverless support is implemented | |
* It currently supports wrapping https, pubsub and firestore handlers. | |
* usage: https.onRequest(wrap((req, res) => {...})) | |
*/ | |
import type {Event} from '@sentry/types'; | |
import type {https} from 'firebase-functions'; | |
import type {onRequest, onCall} from 'firebase-functions/lib/providers/https'; | |
import type {ScheduleBuilder} from 'firebase-functions/lib/providers/pubsub'; | |
import type {DocumentBuilder} from 'firebase-functions/lib/providers/firestore'; |
"explorer.fileNesting.enabled": true, | |
"explorer.fileNesting.expand": false, | |
"explorer.fileNesting.patterns": { | |
"pubspec.yaml": ".flutter-plugins, .packages, .dart_tool, .flutter-plugins-dependencies, .metadata, .packages, pubspec.lock, build.yaml, analysis_options.yaml, all_lint_rules.yaml", | |
".gitignore": ".gitattributes, .gitmodules, .gitmessage, .mailmap, .git-blame*", | |
"readme.*": "authors, backers.md, changelog*, citation*, code_of_conduct.md, codeowners, contributing.md, contributors, copying, credits, governance.md, history.md, license*, maintainers, readme*, security.md, sponsors.md", | |
"*.dart": "$(capture).g.dart, $(capture).freezed.dart", | |
}, |
As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.
(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))
**1.