Licensed under the Apache License, Version 2.0; you may not use this app except in compliance with the License. You may obtain a copy of the License at https://opensource.org/licenses/Apache-2.0.
Protobufs used by the server and apps in the company "Gislaine Studio" in Andradina-SP, Brazil.
This project is a submodule of the front-end and back-end.
- To add to your project use the following command (only add it if it's not already in the file
.gitmodules).
git submodule add https://github.com/NatanAmorim/gs_protobufsIf this is your first time after adding it to the repository, you need to use init first:
git submodule initTo update on your local project, use one of the following commands.
git submodule update --initgit submodule update --recursive --remote- Style Guide documentation for File Structure and naming conventions.
- gRPC Guides
- Language Guide (proto 3) covers how to use the version 3 of Protocol Buffers in your project.
- gRPC uses a set of well defined status response codes as part of the RPC API.
- Google Common Types This package contains definitions of common types for Google APIs.
- Protobuf 3 support for Visual Studio Code with the extension vscode-proto3.
Important
"optional" does not mean "nullable" in Protobuf.
"optional int32" != "int?"
An optional field is in one of two possible states:
- the field is set, and contains a value that was explicitly set or parsed from the wire. It will be serialized to the wire.
- the field is unset, and will return the default value. It will not be serialized to the wire. You can check to see if the value was explicitly set.
For nullable on C# use Wrapper Type Fields from wrappers.proto.
We prefer all communications to be in English or Portuguese.
This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new Issue.
For help and questions about using this project, please uses the GitHub discussions.
If you believe you have found a security vulnerability in this software, we encourage you to inform us immediately. We will investigate all legitimate reports and do our best to quickly correct the issue.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
- Fork the repository and clone it to your local machine.
- Create a new branch for your changes:
git checkout -b my-new-feature - Make your changes and commit them:
git commit -am 'Add some feature'- Include tests that cover your changes.
- Update the documentation to reflect your changes, where appropriate.
- Add an entry to the
CHANGELOG.mdfile describing your changes if appropriate.
- Push your changes to your fork:
git push origin my-new-feature - Create a pull request from your fork to the main repository.
gh pr create(with the GitHub CLI)
- Clearly describe what you aim to add or fix.
- Try to minimize code changes and use existing style/functions.
If you find a bug, please report it by opening a new issue in the issue tracker. Please include as much detail as possible, including steps to reproduce the bug and any relevant error messages.
To better respond to issues please follow these general guidelines when explaining the problem.
- Clearly describe what you aim to fix, if relevant attach output/logs/screenshots.
- Describe how developers can reproduce the bug.