Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[FEATURE][TWEAK] AccessWeaponBlocker #920
base: master
Are you sure you want to change the base?
[FEATURE][TWEAK] AccessWeaponBlocker #920
Changes from 9 commits
420f50f
253b6a7
2b822c2
a1c3a2c
b4b9448
fe28acd
19993d3
5b88ddb
85bfd8e
78e5a1b
34af9b3
b27c26b
641e5ad
7d75b57
6c93971
613de9c
7e8c070
cd3c7d6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / build (ubuntu-latest)
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / build (ubuntu-latest)
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / Test Packaging
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / Test Packaging
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / YAML Linter
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / YAML Linter
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / build (ubuntu-latest)
Check failure on line 4 in Content.Shared/Backmen/AccessWeaponBlockerSystem/SharedAccessWeaponBlockerComponent.cs
GitHub Actions / build (ubuntu-latest)
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.
Исправьте синтаксическую ошибку в объявлении пространства имен
В строке с объявлением пространства имен присутствует двойная точка с запятой, что является синтаксической ошибкой.
📝 Committable suggestion
🧰 Tools
🪛 GitHub Check: build (ubuntu-latest)
[failure] 4-4:
Type or namespace definition, or end-of-file expected
[failure] 4-4:
Type or namespace definition, or end-of-file expected
🪛 GitHub Check: YAML Linter
[failure] 4-4:
Type or namespace definition, or end-of-file expected
[failure] 4-4:
Type or namespace definition, or end-of-file expected
🪛 GitHub Check: Test Packaging
[failure] 4-4:
Type or namespace definition, or end-of-file expected
[failure] 4-4:
Type or namespace definition, or end-of-file expected